DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=QBk19tfkqKZHDVnrSN/4VPv2iZA1mnaOlOgTb9dcPz/Z6QpxLyxaj
	gXRv5Ut0ZSf3QFGHgO80PCoex2exB88IbExagaezsUf0IP2xNRfrmbdBCzZXv6vs
	PsiwmmK6C3dffzZAyPPQ7Ei/VYF4UZu073iAH8xaEAA8lZTcIKX234=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 16 Feb 2015 22:01:32 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: slow startup after upgrade
Message-ID: <20150216210132.GM8493@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20150213085748 DOT GN7818 AT calimero DOT vinschen DOT de> <1F2D7140EF4B469B90335ECF0A5690CB AT Tamar>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="1ou9v+QBCNysIXaH"
Content-Disposition: inline
In-Reply-To: <1F2D7140EF4B469B90335ECF0A5690CB@Tamar>
User-Agent: Mutt/1.5.23 (2014-03-12)

--1ou9v+QBCNysIXaH
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.=20=20=20=20=20
>=20
> 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.)
>=20
> 1) Running cygwin "echo.exe" from a cmd.exe command shell
>=20
> a) With passwd: files and group: files in /etc/nsswitch.conf
>   0.03 - 0.4 s
>=20
> b) With 1.7.34 and default /etc/nsswitch.conf
>=20
>   around 120s
>=20
> C) With 1.7.35 and default /etc/nsswitch.conf
>=20
>   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

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

--1ou9v+QBCNysIXaH
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJU4lqsAAoJEPU2Bp2uRE+gaA4P+gKkdGpYAuUtSFsGZ89oIMmX
LpBVIUaNZ+U9jg/SlLux2YBRS//1raLzEe94axbNseKhqTozB53NKBgX0YbWbLGC
IMCoWnSuz4xbIXrTLRt9SNp5nEUOfCiFNDm/8j5knZg8T2qdH2BjlEmtEj/DjOXt
sq7QU3/ilTJ17OTBqKB1CaQQz1ugQXnR5O1zWaxSVCIn0CGxU11/kZ1CLagddRPJ
KcmhbhJd/Vaeh2g1fuLxb3lE5G3fJgvRum+9+EDuYCMHzakSRacDuLE2jBVHukQu
BGcs3VR+wi7NWFLbe0XM8UIheno2iRoJbBCrB6or+thWSA2KM4o5mvDOtm+M2udY
p0BxrMidDfOy858FF3/JfqmCSCszp2kt7Wjw6s74+3XmNhywfSbkRMKvmoKz0tZP
zOiM1hhrz7jYkMP0/iFKRUSN/DQ+kH3Iy62r2api9RvioYCiKaFXTz5kADtRk/jD
67AumO8V5eo2runl8XVPm5grz3g/d9zUqE/DGl/xHIA7usRV0WDyq/8TJvoNA+Dv
RUdRFqc5ikQ4i2e6qGxLHFdKZR/bxldWGBN+UzS10DD1DUXdDG1TRcPBQ0XuaU2M
XFuxpyKPbyCNqo+6Iqfi+KldOABvpl7L9pZuKD3uFpEg7UxbBo4qMjDidGISXMTC
HL1JY4Yt99Wg3QEampG9
=Qakm
-----END PGP SIGNATURE-----

--1ou9v+QBCNysIXaH--