unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ilya Zakharevich <nospam-abuse@ilyaz.org>, emacs-devel@gnu.org
Subject: Re: [PATCH] 5x speedup of flyspell-buffer
Date: Fri, 14 Apr 2023 08:39:10 +0200	[thread overview]
Message-ID: <87ildzm0dz.fsf@web.de> (raw)
In-Reply-To: <833553ggl9.fsf@gnu.org>

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


Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Thu, 13 Apr 2023 13:29:33 -0700
>> From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
>> Cc: emacs-devel@gnu.org
>> 
>> On Thu, Apr 13, 2023 at 01:32:11PM +0300, Eli Zaretskii wrote:
>> > > Without profiling, how to find out “how much overhead is tolerable to
>> > > the user”?!
>> > 
>> > Since you say the change you propose speeds up by a factor of 5, just
>> > setting N = 5 should do approximately the same, no?  I'd actually go
>> > with N = 10 for a good measure.
>> 
>> Nope.  My solution decreases THE OVERHEAD 50 times.  This SPEEDS UP
>> the whole brouhaha ∼5x (since the overhead was 4x). 
>
> OK, then N = 50 should do the same trick.

Wouldn’t that then show too few messages for small buffers?

I quite like the logarithmic message showing, because it ensures that
the user is informed of progress while avoiding a constant spew of
messages.

The only thing I worry about is that there may at some point be too few
messages, so a maximum might be useful to ensure that there is some
progress notification at least once every few seconds. Otherwise users
could think that it stalled.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2023-04-14  6:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 13:50 [PATCH] 5x speedup of flyspell-buffer Ilya Zakharevich
2023-04-13  6:54 ` Eli Zaretskii
2023-04-13 10:23   ` Ilya Zakharevich
2023-04-13 10:32     ` Eli Zaretskii
2023-04-13 20:29       ` Ilya Zakharevich
2023-04-14  5:47         ` Eli Zaretskii
2023-04-14  6:39           ` Dr. Arne Babenhauserheide [this message]
2023-04-14  6:54             ` Eli Zaretskii
2023-04-15  1:51     ` interacting during (sit-for 0). Was: " Ilya Zakharevich
2023-04-15  2:01       ` Ilya Zakharevich

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=87ildzm0dz.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=nospam-abuse@ilyaz.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).