From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: last snapshot is not better than previous version
Date: Tue, 31 May 2016 16:38:00 -0000 [thread overview]
Message-ID: <20160531091651.GB24015@calimero.vinschen.de> (raw)
In-Reply-To: <6FE1A983-9CCD-4010-99DE-FEAA0BA6749E@Denis-Excoffier.org>
[-- Attachment #1: Type: text/plain, Size: 2291 bytes --]
On May 30 19:00, Denis Excoffier wrote:
>
> > On 2016-05-30 10:25, Corinna Vinschen wrote:
> >
> >
> > 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
>
> Thank you for your answer. However, i do insist.
> I use again the file created with "seq 10000 > 10k" and still
> look-up the string "9999" inside it.
>
> I perform:
> strace -o vi.out /usr/bin/vim 10k
> and inside vi:
> :0
> /9999
> :q
>
> Without snapshot, vi.out contains 15133 lines
> With snapshot, vi.out contains 426553 lines. Huh?
I tested with 2.5.1, with the latest snapshot and with the latest from
git master, on 32 and 64 bit. In all cases, the above results in about
1000 'select_stuff::cleanup: calling cleanup routines' lines in vi.out,
give or take, depending on my typing speed.
> Without snapshot, the 6 lines:
> ------------------------------
> select: sel.always_ready 0
> select: sel.wait returns 0
> select_stuff::cleanup: calling cleanup routines
> select_stuff::destroy: deleting select records
> select: recalculating ms
> select: ms now 0
> ------------------------------
> occur about 450 times
>
> With snapshot, the 6 lines:
> ------------------------------
> select: sel.always_ready 0
> select: sel.wait returns 0
> select_stuff::cleanup: calling cleanup routines
> select_stuff::destroy: deleting select records
> select: recalculating us
> select: us now 0
> ------------------------------
> occur more than 69000 times
>
> Something is probably wrong near here. Please tell me what i should experiment next.
>
> Al least i have found a wrong line in select.cc: line 4, the copyright year is missing. ;-)
Yeah, no worries.
Again, I can *not* reproduce this. Maybe we should start at the basics,
a cygcheck output. What's your OS? I'm testing on a 64 bit W10.
What's your terminal? I tried from Mintty as well as from a console.
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 --]
next prev parent reply other threads:[~2016-05-31 9:17 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
2016-05-30 22:41 ` Denis Excoffier
2016-05-31 16:38 ` Corinna Vinschen [this message]
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=20160531091651.GB24015@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).