From: Richard Stallman <rms@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: The current state of the comment-cache branch
Date: Sat, 24 Dec 2016 13:54:27 -0500 [thread overview]
Message-ID: <E1cKrSd-0001hQ-1u@fencepost.gnu.org> (raw)
In-Reply-To: <20161223215056.GA2771@acm.fritz.box> (message from Alan Mackenzie on Fri, 23 Dec 2016 21:50:56 +0000)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> First forward run Backwards Second forward run
> master: 34.100s 36.050s 34.575s
> comment-cache: 30.110s 32.275s 34.990s
Judging by those figures, it seems to be a rather small improvement.
Is it worth adding complexity to get a 13% speedup in one operation?
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
next prev parent reply other threads:[~2016-12-24 18:54 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 21:50 The current state of the comment-cache branch Alan Mackenzie
2016-12-24 1:32 ` Stefan Monnier
2016-12-24 9:07 ` Alan Mackenzie
2016-12-24 1:33 ` Stefan Monnier
2016-12-24 8:40 ` Alan Mackenzie
2016-12-24 20:56 ` Stephen Leake
2016-12-25 15:47 ` Stefan Monnier
2016-12-25 20:41 ` Richard Stallman
2016-12-24 8:02 ` Eli Zaretskii
2016-12-24 8:30 ` Alan Mackenzie
2016-12-24 8:55 ` Eli Zaretskii
2016-12-24 9:42 ` Alan Mackenzie
2016-12-24 11:11 ` Elias Mårtenson
2016-12-24 11:36 ` Alan Mackenzie
2016-12-24 12:00 ` Eli Zaretskii
2016-12-24 21:48 ` Andreas Röhler
[not found] ` <CADtN0W+7zHzuoWFrzs6MuonUM74D_dC+yh10rSk+r0nuxgeTBg@mail.gmail.com>
[not found] ` <CADtN0WJYXRg=oEBxn3UPjF6RFJG62nG4GpUFaphdkj9Egde_4Q@mail.gmail.com>
2016-12-24 12:21 ` Elias Mårtenson
2016-12-27 17:55 ` Alan Mackenzie
2016-12-28 15:36 ` Eli Zaretskii
2016-12-28 16:42 ` Alan Mackenzie
2016-12-28 16:45 ` Nikolaus Rath
2016-12-28 17:09 ` Eli Zaretskii
2016-12-28 23:58 ` Nikolaus Rath
2016-12-29 3:43 ` Eli Zaretskii
2016-12-29 16:56 ` Nikolaus Rath
2016-12-29 17:46 ` Eli Zaretskii
2016-12-29 19:44 ` Alan Mackenzie
2016-12-30 10:29 ` Andreas Röhler
2017-01-03 17:39 ` Stefan Monnier
2017-01-20 18:58 ` Andreas Röhler
2017-01-20 21:48 ` Stefan Monnier
2017-01-21 9:06 ` Andreas Röhler
2017-01-22 4:28 ` Stefan Monnier
2016-12-28 17:15 ` Stefan Monnier
2016-12-29 1:38 ` Richard Stallman
2016-12-29 2:15 ` Stefan Monnier
2016-12-24 12:27 ` Eli Zaretskii
2016-12-24 22:19 ` Paul Eggert
2016-12-25 16:07 ` Stefan Monnier
2016-12-25 16:30 ` Eli Zaretskii
2016-12-28 8:37 ` Alan Mackenzie
2016-12-28 17:02 ` Stefan Monnier
2016-12-28 17:10 ` Stefan Monnier
2016-12-27 16:40 ` Alan Mackenzie
2016-12-28 15:35 ` Eli Zaretskii
2016-12-28 16:35 ` Alan Mackenzie
2016-12-24 18:54 ` Richard Stallman [this message]
2016-12-27 16:11 ` Alan Mackenzie
2016-12-28 1:40 ` Dmitry Gutov
2016-12-28 7:54 ` Alan Mackenzie
2016-12-29 1:13 ` Dmitry Gutov
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=E1cKrSd-0001hQ-1u@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.