From: David Kastrup <dak@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
bruce.connor.am@gmail.com, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 29c360e: Ensure redisplay after "C-x C-e"
Date: Sun, 08 Nov 2015 17:07:40 +0100 [thread overview]
Message-ID: <87bnb4h3ub.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <a1ecdbba-41b2-406d-8334-e80e1f6e9777@default> (Drew Adams's message of "Sun, 8 Nov 2015 07:55:48 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
>> 5% slowdown in overall operation for addressing a redisplay quirk seems
>> like a bad tradeoff. Redisplay quirks are a dime a dozen, after all.
>
> 5% performance hit each
> X 1 dozen
> -----------------------
> 60% performance hit per dozen
It's more like a dime will buy you 100*(1.05^12 - 1)%, close to 80%.
Just for an automatic mode-line update. And it's not like the mode line
is not _documented_ to require a manual kick after changes.
--
David Kastrup
next prev parent reply other threads:[~2015-11-08 16:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151106093011.17282.48378@vcs.savannah.gnu.org>
[not found] ` <E1ZudLX-0004XR-KP@vcs.savannah.gnu.org>
2015-11-06 14:18 ` [Emacs-diffs] master 29c360e: Ensure redisplay after "C-x C-e" Stefan Monnier
2015-11-06 14:31 ` Eli Zaretskii
2015-11-06 14:53 ` Artur Malabarba
2015-11-06 15:30 ` Eli Zaretskii
2015-11-06 16:11 ` Artur Malabarba
2015-11-06 16:30 ` Eli Zaretskii
2015-11-06 19:25 ` Eli Zaretskii
2015-11-07 23:41 ` Stefan Monnier
2015-11-08 3:36 ` Eli Zaretskii
2015-11-08 9:23 ` David Kastrup
2015-11-08 15:54 ` Eli Zaretskii
2015-11-08 15:55 ` Drew Adams
2015-11-08 16:07 ` David Kastrup [this message]
2015-11-08 22:25 ` Stefan Monnier
2015-11-09 3:32 ` Eli Zaretskii
2015-11-06 15:33 ` Stefan Monnier
2015-11-06 15:30 ` Stefan Monnier
2015-11-06 15:47 ` Eli Zaretskii
2015-11-06 15:54 ` Eli Zaretskii
2015-11-06 21:47 ` Stefan Monnier
2015-11-07 9:07 ` Eli Zaretskii
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=87bnb4h3ub.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.