public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: last snapshot is not better than previous version
Date: Mon, 30 May 2016 09:01:00 -0000	[thread overview]
Message-ID: <20160530082547.GB12694@calimero.vinschen.de> (raw)
In-Reply-To: <90DB300A-9605-4E19-BEFC-AFBFB5240C0E@Denis-Excoffier.org>

[-- Attachment #1: Type: text/plain, Size: 2405 bytes --]

Hi Denis,

On May 26 19:21, Denis Excoffier wrote:
> Hello,
> 
> I tried the snapshot dated 2016-05-20. Okay, this one was not announced.
> 
> Functionally it seems ok. But some simple tasks now take a lot of time compared to the last non-snapshot version (2.5.1):
> 
> 1) searching into a small text file
> A simple text file (created with "seq 10000") takes several seconds to load in vim. Lookup for the string "9999" then takes 5 seconds. Previously, searching "9999999" in a bigger file (created with "seq 10000000") used to take 2 seconds only.

I can't reproduce this.

> Note: The "seq 10000000 > myfile" itself makes no notable difference.
> 
> 2) ls in a large directory
> My /usr/bin contains 8098 files. Previously, a plain "ls -F" in this folder took some initialization time (2 seconds), then the display of the files was quite instantaneous. With the new snapshot, the initialization (stat and sort) takes more or less the same time, but afterwards, each single line is displayed at a visible pace, a clear screen is executed after each set of ~24 lines and the whole directory is listed in about 10 minutes.

I can't reproduce this either.

> Note: "ls | wc -l" itself makes no notable difference.
> 
> This occurs under X-Windows (xterm) or not (login window). Under x86, Windows 7. I switched back to 2.5.1.
> 
> This message just in case it could be useful.

The problem is, there's no change at all in the snapshot which would
explain a slowdown of such basic functions:

- Assorted select(2) improvements:

  commits a23e6a35d896a075640db714b28ce74bb6b8d7ff
          e5665d8c930485d5ac6d8913573e27b9e5043d92

- There's a change to the sched_* functions, which is used only rarely
  and which doesn't introduce any waits or loops.

  commits 450f557feee5dd4900e3fd4f16cbb6cabe89fbc6
          4b51e4c142445c133d6075d2a68ce98e8ec6058b

- Fix a size restriction to 2 GB areas

  commit 0aa738220bb9dea2ad479e484560767b36701947

- Replace toupper with explicit tests of character values in the rare
  case TZ isn't set

  commit 030d86d04dbd6ae878ff894256c5a465890d5970

And that's it.  All other changes since 2.5.1 only affect non-Cygwin
targets in newlib and libgloss.


Corinna

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-30  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 19:26 Denis Excoffier
2016-05-30  9:01 ` Corinna Vinschen [this message]
2016-05-30 22:41   ` Denis Excoffier
2016-05-31 16:38     ` Corinna Vinschen
2016-06-04  3:52       ` John Hood
2016-06-04 19:15         ` Denis Excoffier
2016-06-06 14:55           ` 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=20160530082547.GB12694@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).