all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs-26 eec71eb: Speed up replace-buffer-contents
Date: Tue, 3 Jul 2018 13:14:29 -0700	[thread overview]
Message-ID: <517756be-f05e-1fd1-afc9-f8b6d47252f2@cs.ucla.edu> (raw)
In-Reply-To: <837emcjezc.fsf@gnu.org>

Eli Zaretskii wrote:
> Profiling shows that 'diag' takes 32% of the CPU time, and
> buffer_chars_equal takes another 45%.  So any significant gains will
> be in buffer_chars_equal, I think.

Yes, that was what my intuition was pointing at as well. Among other things, we 
can fix the quit problem without having a rbc_quitcounter variable.

I typically measure effectiveness of performance tweaks when using the 
'configure' default of CFLAGS='-g3 -O2', since that's how it's typically built 
downstream. If this particular problem is all about CFLAGS=-O0 please let me 
know, as I guess I can look at that too (but would rather not).



  reply	other threads:[~2018-07-03 20:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180629135646.6054.66405@vcs0.savannah.gnu.org>
     [not found] ` <20180629135648.5C95A2053B@vcs0.savannah.gnu.org>
2018-07-03  2:25   ` emacs-26 eec71eb: Speed up replace-buffer-contents Glenn Morris
2018-07-03  6:25     ` Paul Eggert
2018-07-03 19:28       ` Eli Zaretskii
2018-07-03 20:14         ` Paul Eggert [this message]
2018-07-04  2:31           ` Eli Zaretskii
2018-07-04  6:36             ` Paul Eggert
2018-07-04 15:09               ` Eli Zaretskii
2018-07-04 18:30                 ` Paul Eggert
2018-07-04 18:40                   ` Eli Zaretskii
2018-07-07 11:57                     ` Eli Zaretskii
2018-07-07 18:22                       ` Paul Eggert
2018-07-07 18:40                         ` Eli Zaretskii
2018-07-04 16:55               ` 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=517756be-f05e-1fd1-afc9-f8b6d47252f2@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.