unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jeff Norden <jnorden@math.tntech.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: A question about overlays and performance.
Date: Sat, 25 Jul 2020 12:24:49 -0500	[thread overview]
Message-ID: <fdeeoz7bj2.fsf@norden.tntech.edu> (raw)
In-Reply-To: <835zabcz8d.fsf@gnu.org> (message from Eli Zaretskii on Sat, 25 Jul 2020 19:53:54 +0300)

Thanks for the fast (nearly instantaneous!) response.
>> Is there a way to predict how many overlays will be "too many" and
>> start to slow thing down?
>
> Thousands.
That's great.  The number of overlays I'd create would certainly be less
than 1000.

>> Does the configuration of the overlays play a role?
>
> What do you mean by "configuration" in this context?

I wondered if the simple overlay layout that I described would have less
of an effect than if they were scattered about and intersected in many
different ways.  But if it takes thousands to affect performance, then
that doesn't really matter for my case.

Thanks again!
-Jeff



  reply	other threads:[~2020-07-25 17:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-25 16:40 A question about overlays and performance Jeff Norden
2020-07-25 16:53 ` Eli Zaretskii
2020-07-25 17:24   ` Jeff Norden [this message]
2020-07-25 17:29     ` Eli Zaretskii
2020-07-26  1:33   ` Ihor Radchenko
2020-07-26 13:56     ` Eli Zaretskii
2020-07-26 14:19       ` Ihor Radchenko
2020-07-26 14:44     ` Stefan Monnier
2020-07-27 11:20       ` Ihor Radchenko
2020-07-28 16:43         ` Jeff Norden
2020-07-28 16:58           ` Yuan Fu
2020-07-28 17:05             ` Eric Abrahamsen
2020-07-29  1:52           ` Ihor Radchenko
2020-07-30 18:21             ` Jeff Norden
2020-07-28 23:53         ` Juri Linkov
2020-07-29  1:36           ` Ihor Radchenko
2020-07-30 23:04             ` Juri Linkov

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=fdeeoz7bj2.fsf@norden.tntech.edu \
    --to=jnorden@math.tntech.edu \
    --cc=eliz@gnu.org \
    --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 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).