From: Alexandre Garreau <galex-713@galex-713.eu>
To: emacs-devel@gnu.org
Subject: Re: Against sqlite3!!!
Date: Thu, 09 Dec 2021 08:12:53 +0100 [thread overview]
Message-ID: <12908535.gTCiKFHhma@galex-713.eu> (raw)
In-Reply-To: <AM9PR09MB49776BB11E725D2F7CAA9F2D966F9@AM9PR09MB4977.eurprd09.prod.outlook.com>
Le merkredo, 8-a de decembro 2021, 7-a horo kaj 11:19 CET Arthur Miller a
écrit :
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>
>
> > David Engster <deng@randomsample.de> writes:
>
>
> >> Yes, and it's slow. The Gnus registry is saved/loaded this way, and
> >> this has annoyed me for years.
>
>
>
> > Yup. The Gnus registry would be well suited to use sqlite directly,
> > though -- it's basically hand-maintaining a (large) database, and
> > sqlite is a good fit for that.
> >
> > That is, I don't think the new normal persistence method would be
> > ideal
> > for the registry.
> >
> > But, yes, the Gnus registry is a good demonstration of why serialising
> > hash tables to disk is unworkable in practice.
>
> Than implement a way for Emacs to dump lisp objects to files faster. It
> would be very useful for Emacs in general.
>
> You will still have to serialize your gnus db to sqlite db, and write it
> to disk via sqlite, so disk access will still be there.
Well, I think, wrt writes, it’s impossible to go faster than just writing
plaintext. But sqlite is here to make *reads* faster, not writes. The
only way I can see to make writes faster without any form of serialization
is just garbage collecting related data together, and directly dumping
memory onto disk, in a native but non-portable format, along with metadata
about the native format, and specific implementations to decode it from
other platforms for each memory format. I’d love to see that. But I
think writing is not the bottleneck that we try to improve here.
next prev parent reply other threads:[~2021-12-09 7:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MN2PR12MB3391BC76A0D05236AC76C94E946E9@MN2PR12MB3391.namprd12.prod.outlook.com>
2021-12-07 8:13 ` Against sqlite3!!! (Was: sqlite3) Qiantan Hong
2021-12-07 9:14 ` Qiantan Hong
2021-12-07 12:49 ` Against sqlite3!!! Colin Baxter 😺
2021-12-07 13:21 ` Stefan Monnier
2021-12-07 13:55 ` Qiantan Hong
2021-12-07 15:51 ` Tassilo Horn
2021-12-07 16:35 ` Qiantan Hong
2021-12-07 18:43 ` Arthur Miller
2021-12-07 19:13 ` Qiantan Hong
2021-12-07 19:34 ` Tassilo Horn
2021-12-08 10:00 ` Yuri Khan
2021-12-07 19:52 ` Stefan Monnier
2021-12-07 13:45 ` Against sqlite3!!! (Was: sqlite3) Zhu Zihao
2021-12-07 14:50 ` Against sqlite3!!! David Engster
2021-12-07 20:00 ` Lars Ingebrigtsen
2021-12-08 6:11 ` Arthur Miller
2021-12-08 6:20 ` Qiantan Hong
2021-12-08 9:21 ` Arthur Miller
2021-12-08 9:28 ` Qiantan Hong
2021-12-09 7:12 ` Alexandre Garreau [this message]
2021-12-09 7:27 ` Qiantan Hong
[not found] ` <24465971.J1OoJ6LT5i@galex-713.eu>
2021-12-09 7:50 ` Qiantan Hong
2021-12-09 19:16 ` Thierry Volpiatto
2021-12-09 19:24 ` Qiantan Hong
2021-12-09 19:28 ` Qiantan Hong
2021-12-09 13:17 ` Stefan Monnier
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=12908535.gTCiKFHhma@galex-713.eu \
--to=galex-713@galex-713.eu \
--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).