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 25 11:15, John Hein wrote:
> Corinna Vinschen wrote at 09:56 +0100 on Feb 25, 2015:
>  > 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...
> 
> Bah... sorry, you should get the name in this response.

Uh, it's you! :)

>  > > 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.
> 
> I'm thinking it's either related to XP or _something_ with the
> particular XP box I'm using (when logged in on the domain, I can't
> disable many group policy things or temporarily inhibit AV, so it's
> harder to find/eliminate something to pin blame on - certainly may not
> be something the latest cygwin is doing when running on XP in a
> "large" AD domain).
> 
> I went to a win 7 box and the 2/24 snap makes mkpasswd -d run in 33
> seconds and enumerates all 8016 entries.  37 seconds with the 2/25
> snap.

The timing should be roughly the same, but fluctuations in the low
percentage range are normal.

> And win 7 doesn't get the 'wrong arg.type' error with the same 2/24
> cygwin1.dll for whatever reason.

Interesting.  I could reproduce this and it was very certainly a bug
in the code, fixed in -25 snapshot and 1.7.35-0.4.

>  > 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!"
> 
> On win7: that command takes .17, .44, .48, .53 sec between 1st & 2nd time stamp
> 
> That had 'db' only for passwd/group in nsswitch.conf, no cygwin procs
> running including cygserver.

Sounds good to me.

> On problematic winxp box:
>     [passwd, group, db_shell: 'files db', 'files db' & /bin/dash]
>       16.83, 17.03, 24.80, 28.79, 27.99, 27.39 sec
> 
>     [passwd, group, db_shell: db, db & /bin/dash]
>       23.51, 27.91, 28.78 sec

Doesn't sound good at all.  Terrible in fact.  That a 32 or 64 bit XP?
I didn't fire up my XP test machines for ages and I'm not overly enjoying
it, but I guess I have to.  Oh well, hang on...

[...time passes...]
[...starting up...]
[...XP...]
[...32 bit...]
[...updating...]
[...testing...]

Hmm, no.  In my case there's no visible delay starting mintty, and tcsh
is my login shell, too.  mkpasswd and mkgroup are running comparably
fast as on my W8.1 64 bit machine I'm using for testing in the first
place.

Something strange is going on on your XP machine, it seems.


Corinna

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

Attachment: pgpT9lBb1YGXC.pgp
Description: PGP signature


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