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=JOa/G85Olm8uB83JNgCaVhC2xgTX1hGR7rapyfrioq2Mkvg/5WEW+
	9BDG75jkbR+QBIhRyA0QCRIS+2Yc0UcrFKnE0tu5hADNghNJL0gWd5AdD0OV8mpK
	f8ILZZh+n1zlNSYb8jWp9xUHaqLuwfX8HsyzeF9VCv4Hkdys0XS+nQ=
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: Wed, 25 Feb 2015 21:28:28 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.35-0.4
Message-ID: <20150225202828.GB9628@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <announce DOT 20150225125112 DOT GB7010 AT calimero DOT vinschen DOT de> <87r3tdpxni DOT fsf AT Rainer DOT invalid>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="1UWUbFP1cBYEclgG"
Content-Disposition: inline
In-Reply-To: <87r3tdpxni.fsf@Rainer.invalid>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

On Feb 25 21:02, Achim Gratz wrote:
> Corinna Vinschen writes:
> > This release introduces a rewrite of the functions being the main
> > culprit for the slowness of fetching account information from AD.
> > There are still a few potential ways to hone the results, but code-wise
> > there isn't a lot left to do anymore.
>=20
> I'll reply here=E2=80=A6
>=20
> I've just tested the latest snapshot (aka the 0.4 release) via VPN.  The
> basic test is starting a mintty from a cmd prompt and have mintty run
> some program depending on the test.  I run two tests, one is just an
> "echo test" which uses the builtin echo of the shell that mintty just
> fired up, the other does a "git status".  Connected via LAN the echo
> tests take all under a second now save for a few excursion when I didn't
> start cygwrunserv that were around 1.5s.  The git test takes a bit
> longer depending on whether I start it on a network share or a local
> directory, but completes in under 2s.
>=20
> Now, connecting via the VPN and not running cygserv I get 2s for the
> echo test and 47/42/6 seconds for git status on two different network
> shares and a local repository (these repositories are all fairly small,
> just some local configuration stuff).  With cygserv running, these times
> change to 1/49/5/5 seconds (yes, it took two seconds longer on one of
> the network shares).
>=20
> As it happens, I can force the VPN to connect almost exactly from the
> other side of the globe, which will produce a long roundtrip time
> (unless you are having a satellite link in there somewhere or really
> stupid routing it can't get much worse than that).  In this case, with
> cygserv running I get 15/840/40/85 seconds.  Without cygserv, this
> becomes 39/789/-/95 (I skipped one of the network shares for this test).
> Again there's one network share that had better performance for the git
> test without cygserv.  Another interesting bit is that the echo test
> time actually depended on whether the working directory was on a network
> share (resulting in 39 seconds) or on the local drive (where it only
> took 26 seconds).
>=20
> So, those changes in the latest snapshot look good from that perspective
> and the remaining delays, at least with cygserv running are in any case
> not attributable to the LDAP integration.  I don't have an old Cygwin
> installation o that machine anymore, but the results w/ cygserv on the
> long latency link match my experience of using that long latency link
> "for real" about a year ago.

I'm still a bit confused by the results.  What "delays" are we looking
at if they are not attributable to LDAP?  Are they "expected" delays
or is that something which is new now?  If it's new, is there a simple
testcase we can use for further debugging, preferredly one with a
single executable showing a certain, debuggable behaviour.  This should
ideally start with an strace to isolate the problem, and then we can
look further.


Thanks,
Corinna

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

--1UWUbFP1cBYEclgG
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJU7jBsAAoJEPU2Bp2uRE+gBssP/2Es21FTpfUf2CVqZ+xkrUtx
oKlAbuQyXKs6vmxuGyoQYXzLQ6ZzYyfyaKrZTwn+inmLRA7T9cE5oR+gmDwwhXGP
8mzVREIP6N6SFaP/4HmxENIwuBuSK2L8ZFOhcvnWhQWSsUe11lmMXQI9LDyeZ7pt
Hnl+drd7lXgWOlxeQUZrj3x3ONwznHK0T6DC+SO4KGz0aq4s/7UvclXjVORwEV52
QCh4W4oltgRyYNz2btQmdVRgkOR7RjNwV5lSxVMbBd1gqGfXyWJ5Sf0GBC2AX0dn
xTN/P0PgouE929hPTrnRf/fDRYhu+PGYh311AsR81fXaRNFrOnsIKO0GQwtp2iCP
Rlqi03EiOUgYKTLINfSZbnKvzRgoTeKMu6ULE0wrX3RIAe+zGeZbQxBxbgDmZx82
iFUGiq6J686V0c/7yW+XuWPqMN8gB3fxotehzWWVnTC74I4LFvEmFg8Ps8gD3F9f
+IlkWp3LmeqrUyNugdukAjrRd1+0DagVSryVT6QwHUGvN/m2MvuvlBXQC4T3ycNx
C0C7CIg1o7JUtiZctF+d07h8Lf87D0Lbt+i3r1cFl5pE0U6J1feI/HGk9JRL4DjU
Ew8/Nv9WZ17XfU/ebyvBRPrSvjcggngm90zxmmiqbcxjaVJJLaxb/I9l4VdFrZgP
hFXZ7ctST+Ed/FBFxlOU
=fxtp
-----END PGP SIGNATURE-----

--1UWUbFP1cBYEclgG--