Gnus development mailing list
 help / color / mirror / Atom feed
From: Wayne Harris <wharris1@protonmail.com>
To: ding@gnus.org
Subject: on a buffer performance test on GNU EMACS 28
Date: Sat, 15 Aug 2020 23:07:00 -0300	[thread overview]
Message-ID: <861rk7xs1n.fsf@protonmail.com> (raw)

On Windows, I said M-x run-python, then said

  for i in range(100000): print(i)

on both GNU EMACS 28 and GNU EMACS 24.  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.  Incredible difference.  I suppose this
will make me upgrade to GNU EMACS 28.

How do you explain this marvelous difference?  Could there i386 versus
i686 have anything to do this?  I would doubt it.

(*) Versions

GNU Emacs 24.3.1 (i386-mingw-nt6.2.9200) of 2013-03-17 on MARVIN
GNU Emacs 28.0.50 (build 1, i686-w64-mingw32) of 2020-07-05



             reply	other threads:[~2020-08-16  2:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-16  2:07 Wayne Harris [this message]
2020-08-16 17:23 ` Eric Abrahamsen
2020-08-17  3:57   ` Wayne Harris
2020-08-19  2:02     ` Wayne Harris
2020-08-19 16:27       ` Eric Abrahamsen
2020-08-20  2:22         ` Rafi Khan
2020-08-20  3:02           ` Eric Abrahamsen
2020-08-20  3:36             ` Wayne Harris
2020-08-20 14:14               ` Wayne Harris
2020-08-20 18:02                 ` Eric Abrahamsen
2020-08-20 21:55                   ` Jason Tibbitts
2020-08-20 22:44                     ` Eric Abrahamsen
2020-08-21  3:52                       ` Wayne Harris
2020-08-21  2:01                     ` 황병희
2020-08-21  0:12                   ` Wayne Harris
2020-08-20  2:57         ` Wayne Harris

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=861rk7xs1n.fsf@protonmail.com \
    --to=wharris1@protonmail.com \
    --cc=ding@gnus.org \
    /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 NNTP newsgroup(s).