From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 49127@debbugs.gnu.org, victor.nawothnig@icloud.com
Subject: bug#49127: Performance degradation in encode_coding_object
Date: Tue, 17 Aug 2021 20:16:29 +0300 [thread overview]
Message-ID: <83wnok56vm.fsf@gnu.org> (raw)
In-Reply-To: <8CDC6E7F-73BF-4810-8218-04CD58316195@acm.org> (message from Mattias Engdegård on Tue, 17 Aug 2021 18:07:10 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Tue, 17 Aug 2021 18:07:10 +0200
> Cc: victor.nawothnig@icloud.com, 49127@debbugs.gnu.org
>
> This business makes me wonder if there are more cases where the linear marker list causes bad performance. Probably not very often but it's not unreasonable for a mode to have many data structures with many (live) markers into the text, and that would lead to text changes going from O(1) to O(text size). In any case, not anything to worry about right now.
It's a problem to have many markers in a buffer. Not only for code
that searches them linearly, but also for stuff like converting
between character and byte positions, something that we do a lot in
the most inner loops of our code. Lisp programs that produce gobs of
markers should be ideally redesigned not to do so. Unless we change
the way we store markers to make that a non-issue.
next prev parent reply other threads:[~2021-08-17 17:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EC5DED64-8465-45A3-B20C-8D21F70E0A34@acm.org>
2021-08-16 17:43 ` bug#49127: Performance degradation in encode_coding_object Eli Zaretskii
2021-08-16 18:06 ` Mattias Engdegård
2021-08-16 18:50 ` Eli Zaretskii
2021-08-16 20:04 ` Mattias Engdegård
2021-08-17 12:34 ` Eli Zaretskii
2021-08-17 13:06 ` Mattias Engdegård
2021-08-17 14:05 ` Eli Zaretskii
2021-08-17 16:07 ` Mattias Engdegård
2021-08-17 17:16 ` Eli Zaretskii [this message]
2021-08-18 11:04 ` Mattias Engdegård
2021-08-18 11:43 ` Eli Zaretskii
2021-08-18 12:21 ` Mattias Engdegård
2021-08-18 13:23 ` Eli Zaretskii
2021-08-18 13:32 ` Mattias Engdegård
2021-08-18 13:39 ` Eli Zaretskii
2021-08-18 13:54 ` Mattias Engdegård
2021-08-18 13:59 ` Eli Zaretskii
2021-08-18 15:24 ` Mattias Engdegård
2021-08-18 14:34 ` Lars Ingebrigtsen
2021-08-20 23:24 ` Michael Welsh Duggan
2021-08-21 6:34 ` Eli Zaretskii
2021-06-20 6:30 Victor Nawothnig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-20 9:04 ` Eli Zaretskii
2021-06-24 16:49 ` Eli Zaretskii
2021-07-25 7:10 ` Eli Zaretskii
2021-08-15 15:07 ` Eli Zaretskii
2021-08-17 12:35 ` 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
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=83wnok56vm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49127@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=victor.nawothnig@icloud.com \
/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).