public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <wyml@etr-usa.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-002
Date: Tue, 09 Dec 2014 22:06:00 -0000	[thread overview]
Message-ID: <D4F27DE4-8F35-458D-B97D-B9CF3C13FB77@etr-usa.com> (raw)
In-Reply-To: <20141209105617.GF3810@calimero.vinschen.de>

On Dec 9, 2014, at 3:56 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:

> On Dec  8 15:14, Warren Young wrote:
>> On Dec 6, 2014, at 12:49 PM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
>> 
>>> - Cygwin can now generate passwd/group entries directly from Windows
>> 
>> don’t use AD here, and /etc/passwd suffices
>> for my purposes
> 
> You can still benefit, I hope.  Even when using only the local SAM, the
> process startups should be a tad bit faster than when every exec'ed
> process has to read /etc/passwd and /etc/group files:

Challenge…accepted.

I decided to do the nastiest thing I could think of to Cygwin: run a configure script. ;)

In my Windows 10 Technical Preview test VM, Cygwin 64 1.7.33 runs the iperf3 configure script in 20 seconds.  On upgrading to 1.7.34-002, without doing anything to nsswitch.conf, the time remained the same.  On making the suggested change to nsswitch.conf, configure time went *up* to 21 seconds.

So, I moved the new nsswitch.conf back out of the way, relaunched MinTTY, and configure time dropped its extra second.

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

  reply	other threads:[~2014-12-09 22:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-06 20:24 Corinna Vinschen
2014-12-07 15:59 ` Henry S. Thompson
2014-12-08 10:50   ` Corinna Vinschen
2014-12-08 22:15 ` Warren Young
2014-12-09 10:56   ` Corinna Vinschen
2014-12-09 22:06     ` Warren Young [this message]
2014-12-10 14:59       ` Corinna Vinschen
2014-12-09 11:50   ` Andrey Repin
2014-12-12 22:42 ` Thomas Wolff
2014-12-15 11:07   ` Corinna Vinschen
2014-12-07 11:21 Angelo Graziosi
2014-12-08 10:49 ` Corinna Vinschen
2014-12-09 23:28 Angelo Graziosi
2014-12-10  4:36 ` Alexey Pavlov
2014-12-10 16:01   ` Corinna Vinschen
2014-12-11  4:37     ` Alexey Pavlov
2014-12-11 17:42       ` Warren Young
2014-12-11 18:20         ` Ray Donnelly
2014-12-10  9:48 ` JonY
2014-12-10 15:08   ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D4F27DE4-8F35-458D-B97D-B9CF3C13FB77@etr-usa.com \
    --to=wyml@etr-usa.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).