From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: fast local-file storage for Gnus
Date: Fri, 13 Jun 2003 10:33:53 -0400 [thread overview]
Message-ID: <4nbrx2cai6.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <rzq7k7r9bm6.fsf@albion.dl.ac.uk> (Dave Love's message of "Thu, 12 Jun 2003 23:25:53 +0100")
On Thu, 12 Jun 2003, d.love@dl.ac.uk wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> I'm sure the implementation will not be hard for people who know
>> autoconf well.
>
> [That might be me, which is why I made the comment! The problem is
> in guessing where on earth the library is, and checking versions.]
Unfortunately there's no libdb-config like for instance imlib2-config,
that sort of wrapper is very useful. I would imagine a --with-libdb
switch, optional and left empty (no libdb) by default, would do the
job. Anyhow, what I want is a generic interface, libdb is just a
container library and I don't want to write specifically for it.
>> It's not a bad approach, but it can be slow with large alists.
>
> You don't actually have to cons an alist to transfer data from a
> file to a hash table. (You can read data directly into a table,
> which is probably faster. If necessary, you could make a primitive
> to dump and restore hash tables fast.)
Right, but I don't know how to write that primitive in C, and in Lisp
it would probably be too slow. If we're going to write that
primitive, why not make it a generic interface with
get/set/delete/commit functions with a plain text backend?
> If you want `fast' access to the data, you presumably have to read
> them into memory anyway, so I think it needs measurements, unless
> you've already made them. I've had surprising results from
> measuring this sort of thing in the past.
I really don't know what to measure, since there's only the
alist-to-plain-file mechanism right now :)
>> Here's what I want, in an ideal world: a new data structure called
>> a persistent-hashtable.
>
> [...]
>
>> Is this possible?
>
> I don't see why not, if it's well designed, but you'd want to talk
> to rms about it and be prepared to do the implementation. I suspect
> it's more difficult to get right than you might guess, but that's
> not a reason for not doing it.
So emacs-devel would be the right place?
Thanks
Ted
next prev parent reply other threads:[~2003-06-13 14:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 20:31 Ted Zlatanov
2003-05-24 11:08 ` Kai Großjohann
[not found] ` <84wuggy548.fsf@lucy.is.informatik.uni-duis?= =?iso-8859-15?q?burg.de>
2003-05-24 12:03 ` Matthias Andree
2003-05-24 13:22 ` Ted Zlatanov
2003-05-24 13:47 ` Matthias Andree
2003-05-24 13:36 ` Kai Großjohann
2003-05-30 13:28 ` Dave Love
2003-05-30 13:57 ` Josh Huber
2003-05-30 15:23 ` Ted Zlatanov
2003-06-03 11:02 ` Dave Love
2003-06-03 15:37 ` Ted Zlatanov
2003-06-12 22:25 ` Dave Love
2003-06-13 14:33 ` Ted Zlatanov [this message]
2003-06-17 22:06 ` Dave Love
2003-06-03 11:00 ` Dave Love
2003-06-03 13:35 ` Kai Großjohann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4nbrx2cai6.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).