From: "Mattias Engdegård" <mattiase@acm.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: 52753@debbugs.gnu.org
Subject: bug#52753: 29.0.50; Printing long list-like structures fails
Date: Sun, 30 Jan 2022 11:16:24 +0100 [thread overview]
Message-ID: <EBE68196-C802-4E2D-8F8C-D7FE19C5AF72@acm.org> (raw)
In-Reply-To: <878ruxd1ni.fsf@localhost>
30 jan. 2022 kl. 10.16 skrev Ihor Radchenko <yantar92@gmail.com>:
> the speedup will only be relevant when
> explicitly allocated C arrays are used to store B-tree segments: all the
> tree data must be physically located within continuous segment of RAM
> address space.
Lisp vectors are contiguous in memory, and your keys are small integers and thus unboxed.
> People do say
> that splay trees can be good, but never have real world examples.
The trouble with splay trees seems to be that they require a very skewed access distribution to be worthwhile -- every read of something that isn't the latest accessed element becomes a tree modification. But that implies that the access pattern exhibits spatial and/or temporal locality, which makes caching an attractive alternative (explicit or those in your computer).
next prev parent reply other threads:[~2022-01-30 10:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 11:07 bug#52753: 29.0.50; Printing long list-like structures fails Ihor Radchenko
2021-12-23 16:11 ` Mattias Engdegård
2021-12-24 10:56 ` Ihor Radchenko
2021-12-24 16:54 ` Mattias Engdegård
2021-12-25 11:15 ` Mattias Engdegård
2022-01-23 12:44 ` Ihor Radchenko
2022-01-23 16:28 ` Mattias Engdegård
2022-01-30 9:16 ` Ihor Radchenko
2022-01-30 10:16 ` Mattias Engdegård [this message]
2022-05-31 10:31 ` Mattias Engdegård
2022-06-02 13:12 ` Ihor Radchenko
2022-06-02 16:10 ` Mattias Engdegård
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=EBE68196-C802-4E2D-8F8C-D7FE19C5AF72@acm.org \
--to=mattiase@acm.org \
--cc=52753@debbugs.gnu.org \
--cc=yantar92@gmail.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).