From: Wayne Harris via "Emacs development discussions." <emacs-devel@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: on a buffer performance test on Windows GNU EMACS 28, 27, 26 and 24
Date: Wed, 26 Aug 2020 22:51:02 -0300 [thread overview]
Message-ID: <86v9h4svp5.fsf@protonmail.com> (raw)
In-Reply-To: 835z963p79.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Tue, 25 Aug 2020 00:35:50 -0300
>> From: Wayne Harris via "Emacs development discussions." <emacs-devel@gnu.org>
>>
>> On Windows, I said M-x run-python, then said
>>
>> for i in range(100000): print(i)
>>
>> on both GNU EMACS 28, 27, 26 and GNU EMACS 24. It turns out GNU EMACS
>> 24 is the slowest. There doesn't seem to be a difference between 28 and
>> 27, but 26 is clearly slower too.
>>
>> I timed the speed of the buffer to scroll up. I used my own phone's
>> stop watch. I started out the slow one first, which was EMACS 24, only
>> after it was running I started the clock, then I started GNU EMACS 28's
>> code. The result was GNU EMACS 28 finishes in less than 8.00 seconds.
>> GNU EMACS 24 finishes after 24.44 seconds. I didn't time 27 and 26, but
>> I couldn't tell any difference between 28 and 27. And 26 was slower
>> than 27 and 28.
>>
>> What is the reason for the difference? Thanks!
>
> We changed the value of w32-pipe-read-delay to zero in Emacs 27,
> that sounds like the likely reason.
Lol. I've been using ``slow'' GNU Emacs 24 for years without ever
thinking I could set a variable and have it speed up quite a bit.
As you know, w32-pipe-read-delay is 50 in GNU Emacs 24 and setting it to
zero makes it as fast as GNU Emacs 27. I don't have to upgrade after
all. But now I did. It's very good to know that I can go back if
somehow I need to. Thank you for the information.
prev parent reply other threads:[~2020-08-27 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 3:35 on a buffer performance test on Windows GNU EMACS 28, 27, 26 and 24 Wayne Harris via Emacs development discussions.
2020-08-26 6:18 ` Eli Zaretskii
2020-08-27 1:51 ` Wayne Harris via Emacs development discussions. [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86v9h4svp5.fsf@protonmail.com \
--to=emacs-devel@gnu.org \
--cc=wharris1@protonmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).