DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=M4nPU
	tzjeL9w7RBBZMEMno9eY+iy/Sflirhs1O6gZ+yhg8xoPLn832z0Vg1s7WdRmiqHh
	bIMUwRzx2HARMWBHsAK055QDhCWjSj1YsBu7I0IUndkvhXYL4tlbTsFu6Znpnaru
	aNdyW5qqJLxCHM2DGEYuOP9e//aIoTS9sCeYvw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.35-0.4
References: <announce.20150225125112.GB7010@calimero.vinschen.de>	<87r3tdpxni.fsf@Rainer.invalid>	<20150225202828.GB9628@calimero.vinschen.de>
Date: Wed, 25 Feb 2015 21:54:37 +0100
In-Reply-To: <20150225202828.GB9628@calimero.vinschen.de> (Corinna Vinschen's	message of "Wed, 25 Feb 2015 21:28:28 +0100")
Message-ID: <87mw41pv8y.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Corinna Vinschen writes:
> 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?

The echo test can be used as a baseline that is most likely dominated by
LDAP responses (not entirely, since there will be a bunch of file
lookups in there as well from the bash to the home drive, which in my
case is remote).  The git tests on the other hand look up, stat and read
a bunch of files on top of that and that data needs to take the full
roundtrip several times.  I've addded those because they are more
representative for my usual workload.

> 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.

I don't think there is a new problem.  A few things are interesting
(like that one network share that somehow makes the cygserver case
slower), but I don't have anything in hand that would permit debugging
and it will be hard to isolate it down to Cygwin anyway since there is
quite a bit of Windows code involved in all that.

In any case, it looks like the behaviour over long latency links is
about back to where it was before LDAP integration at least when one
uses cygserver for caching.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple