From: Aaron Jensen <aaronjensen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31853@debbugs.gnu.org
Subject: bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers
Date: Sun, 17 Jun 2018 05:37:41 -0700 [thread overview]
Message-ID: <CAHyO48yO82pFTuGBVsQADXD5s6XH0Z5nF=8SGrGus-UC7AN9GA@mail.gmail.com> (raw)
In-Reply-To: <CAHyO48yxkHA=XzJ12fxGsp0AWqpHdgZCBE=qDuLkcFZhe3HOyQ@mail.gmail.com>
> On Sat, Jun 16, 2018 at 12:53 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > In https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18522#201 I proposed
> > a change to set-default that would use FOR_EACH_LIVE_BUFFER. Could
> > you see if that change helps in your case?
With 148 live buffers and 6 hours of uptime, I'm up to about 23
microseconds. Still a far cry from 1ms. I'll keep testing.
next prev parent reply other threads:[~2018-06-17 12:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 1:42 bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers Aaron Jensen
2018-06-16 2:10 ` bug#31853: (27.0.50; binding case-fold-search is slow when there are many buffers) Aaron Jensen
2018-06-16 6:51 ` bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers Eli Zaretskii
2018-06-30 13:18 ` bug#31853: (27.0.50; binding case-fold-search is slow when there are many buffers) Stefan Monnier
2018-06-30 13:53 ` Eli Zaretskii
2018-06-16 2:17 ` bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers Noam Postavsky
2018-06-16 6:52 ` Eli Zaretskii
2018-06-16 13:51 ` Noam Postavsky
2018-06-16 6:45 ` Eli Zaretskii
2018-06-16 7:39 ` Aaron Jensen
2018-06-16 7:53 ` Eli Zaretskii
2018-06-16 14:54 ` Aaron Jensen
2018-06-17 12:37 ` Aaron Jensen [this message]
2018-06-17 13:11 ` Eli Zaretskii
2018-06-23 5:23 ` Aaron Jensen
2018-06-23 6:54 ` Eli Zaretskii
2018-06-30 8:19 ` Eli Zaretskii
2018-06-30 18:22 ` Aaron Jensen
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='CAHyO48yO82pFTuGBVsQADXD5s6XH0Z5nF=8SGrGus-UC7AN9GA@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=31853@debbugs.gnu.org \
--cc=eliz@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).