public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: X11 forwarding extremely slow (unusable) after Cygwin upgrade (starting from cygwin1.dll version 3.1.0-0.4)
Date: Sat, 04 Jan 2020 01:51:00 -0000	[thread overview]
Message-ID: <20200104105142.699b9d6f7a518b51ea24b738@nifty.ne.jp> (raw)
In-Reply-To: <535e7760-f4da-2018-1dee-1c9bf2ea6cc9@cornell.edu>

On Thu, 2 Jan 2020 22:16:02 +0000
Ken Brown wrote:
> I think this narrows it down to one of the following commits:

I looked into this probelm and found the issue occurs after
the following commit.

> commit 915fcd0ae8d83546ce135131cd25bf6795d97966
> Author: Takashi Yano <takashi.yano@nifty.ne.jp>
> Date:   Thu Sep 5 13:22:54 2019 +0900
> 
>      Cygwin: pty: Fix select() with pseudo console support.

I investigated this deeper, and found:

1) xterm in ssh -Y session calls select() about 1000 times
   at startup.
2) pi->thread->detach() in pty_slave_cleanup() takes about
   20usec in usual, however, it takes more than 10msec
   in ssh -Y session.

As a result, start up of xterm takes more than 10 sec.

I have no idea so far why cygthread::detach() becomes
so slow in ssh -Y session. :-(

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2020-01-04  1:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 21:26 ianpul01
2020-01-02 22:16 ` Ken Brown
2020-01-04  1:51   ` Takashi Yano [this message]
2020-01-06 14:40     ` Takashi Yano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200104105142.699b9d6f7a518b51ea24b738@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).