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 24 16:03, q2t2hzmwuk@snkmail.com wrote:
> Corinna Vinschen corinna-cygwin-at-cygwin.com |cygwin_ml_nodigest| wrote at 22:13 +0100 on Feb 24, 2015:
>  > Hi Roger,
>  >
>  > On Feb 24 19:55, Roger Orr wrote:
>  > > Hello Corinna,
>  > > It seems slightly faster than the previous patch and I've not noticed a
>  > > downside yet.
>  > >
>  > >
>  > > CYGWIN_NT-6.1-WOW LCLDN-DEV24 1.7.35s(0.286/5/3) 20150220 15:47:55 i686
>  > > Cygwin:
>  > >
>  > > ~37ms to run echo.exe from Windows command prompt
>  > > ~60ms to run .\id.exe -a from Windows command prompt
>  > >
>  > > CYGWIN_NT-6.1-WOW LCLDN-DEV24 1.7.35s(0.286/5/3) 20150223 21:02:38 i686
>  > > Cygwin:
>  > >
>  > > ~35ms to run echo.exe from Windows command prompt
>  > > ~53ms to run .\id.exe -a from Windows command prompt
>  >
>  > That's a nice result.
>  >
>  > However, I don't quite understand this result for the older DLL.
>  > Weren't you reporting >4 secs as startup time from 1.7.35?!?
>  >
>  > On another note:
>  >
>  > I just uploaded a new developer snapshot (2015-02-24).  This snapshot
>  > should improve mkpasswd/mkgroup or, generally speaking, enumerating AD
>  > accounts, a lot.  Can you give it a try?
>  >
>  > While you're at it, does the new snapshot still stop after 3.5K accounts
>  > even though you think there are 8K accounts?  If so, I'd be interested
>  > to investigate this further.  The reason is, while testing my today's
>  > performance improvements, I stumbled over a bug in my code which also
>  > resulted in enumerating less accounts as desired.  So I'm not entirely
>  > sure your problem isn't related to a bug either.
> 
> That mkpasswd symptom was reported by me

Really?  This is the first time I see your email address on this ML, and
there's no name connected to it, so I don't even know if you're usually
writing under another email address.  At least a forename would be nice...

> (well, maybe others, too).
> I'm running it again, but it's still very slow, AFAICS.

It shouldn't.  It performs only one LDAP call now per 100 accounts,
If that's still slow in your environment, I don't see any way to
speed this up any further.

> I'll report
> how long it took when / if it finishes.
> 
> New issue with recent snaps:
> 
> Running the 20150224 (and *23) snapshot produces the following on Win
> XP (yes, I know) if cygserver is running:

Sidenote: I'm contemplating to stop supporting XP end of this year.

> $ /usr/sbin/syslog-ng -F
>       1 [main] syslog-ng 5776 C:\cygwin\usr\sbin\syslog-ng.exe: *** fatal error - Fetching account info from cygserver with wrong arg.type 2

Try the snapshot I just uploaded (2015-02-25).  I forgot a tiny, but
crucial statement in the code when I changed that code two days ago.
That should be fixed now.

> tcsh still taking a long time here (also XP - 3+ minutes with
> cygserver running).  bash & dash much quicker.

Works very quickly for me.  Problem is, I don't know anything about
your environment.  Are you working remote or in an office?  How many
groups are in your user token?  What is the result of this funny
little statement Dennis created:

  cmd /v:on /c "echo !TIME! & C:\cygwin64\bin\mintty.exe /bin/echo "test" & echo !TIME!"


Corinna

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

Attachment: pgpeAk_1SHGfD.pgp
Description: PGP signature


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