unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Alan Mackenzie <acm@muc.de>
Cc: Eli Zaretskii <eliz@gnu.org>, John Wiegley <johnw@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: 33% speed up in CC Mode scrolling.
Date: Mon, 27 Jun 2016 19:28:55 +0200	[thread overview]
Message-ID: <57716257.5040304@gmx.at> (raw)
In-Reply-To: <57714FDD.1070604@gmx.at>

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

 > font-lock-maximum-decoration  elapsed  average
 > 3                             1.999    0.012
 > 2                             1.765    0.010
 > 1                             1.466    0.009
 >
 > In comparison the optimized build with ‘font-lock-maximum-decoration’ 3
 > gets me:
 >
 > 3                             0.409    0.002

These tests actually time scrolling only so they are misleading.  Using
the modified attached file the results below are more accurate: R stands
for the release branch, M for master, and O for an optimized build of
master.  The following number is the ‘font-lock-maximum-decoration’
value - 1, 2 or 3.  So R3 stands for the release branch with decoration
level 3.  The second column is the elapsed, the third the average time.

R3     109.61000000  0.6485798816
M3      79.62599999  0.4711597633
O3      11.516       0.0681420118
R2      23.71799999  0.1403431952
M2      25.35900000  0.1500532544
R1      19.32799999  0.1143668639
M1      20.406       0.1207455621

So there is a significant speed up from R3 to M3 and the speed up of M3
to M2 is by a factor of 3 approximately.  With decoration levels 2 and 1
master is slightly slower than the release branch here.

martin

[-- Attachment #2: test2.el --]
[-- Type: application/emacs-lisp, Size: 660 bytes --]

  reply	other threads:[~2016-06-27 17:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 22:20 33% speed up in CC Mode scrolling Alan Mackenzie
2016-06-16  0:41 ` John Wiegley
2016-06-16  1:02 ` Clément Pit--Claudel
2016-06-16 23:15   ` Richard Stallman
2016-06-17 15:38     ` Alan Mackenzie
2016-06-19 17:21       ` Richard Stallman
2016-06-20  0:44         ` Stefan Monnier
2016-06-20 23:04           ` Richard Stallman
2016-06-21  0:47             ` Stefan Monnier
2016-06-22  6:34               ` Richard Stallman
2016-06-27  6:31 ` martin rudalics
2016-06-27 12:49   ` Alan Mackenzie
2016-06-27 16:10     ` martin rudalics
2016-06-27 17:28       ` martin rudalics [this message]
2016-06-27 18:44         ` Alan Mackenzie
2016-06-28  8:23           ` martin rudalics
2016-06-28 10:27             ` Alan Mackenzie
2016-06-27 16:28   ` Eli Zaretskii
2016-06-27 16:57     ` martin rudalics
2016-06-27 19:31       ` Eli Zaretskii
2016-06-28  8:23         ` martin rudalics
2016-06-28  9:18           ` Alan Mackenzie

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=57716257.5040304@gmx.at \
    --to=rudalics@gmx.at \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@gnu.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.
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).