This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: slow startup after upgrade


On Feb 16 20:02, Roger Orr wrote:
> Corinna Vinschen wrote:
> > So I'd think the best way forward is to update to the
> > 1.7.35-0.1 test release and report further from there.     
> 
> Thanks, this does help a little. However I will still be using the 'files'
> setting.

The idea was to test this stuff to find a better solution which is
acceptable.  If you simply revert to "files" without helping to test
we'll probably never find the culprit.

> Here are some results in case they're of interest. (Windows 7/64 with
> cygwin/64.)
> 
> 1) Running cygwin "echo.exe" from a cmd.exe command shell
> 
> a) With passwd: files and group: files in /etc/nsswitch.conf
>   0.03 - 0.4 s
> 
> b) With 1.7.34 and default /etc/nsswitch.conf
> 
>   around 120s
> 
> C) With 1.7.35 and default /etc/nsswitch.conf
> 
>   4.4 - 4.6s

Much better, but...

...what's going on with your AD?!?  There are only a couple of calls to
LookupAccountSid (one for your user account, one per group in your user
token) and a single LDAP call fetching a handful of attributes for your
user account.  This shouldn't really require 4 secs.

It would be nice to know what part of the code is so slow.  The
LookupAccountSid calls shouldn't be so slow because they only fetch
information already cached on the local machine.  So it's probably
the LDAP call.  Why does an LDAP call take 4 secs?!?

Are you remote from your DC, by any chance?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgpmyp485VQ6V.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]