From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org, proff@iq.org
Subject: Re: nnsql.el ?
Date: 07 Oct 1999 11:15:43 +0200 [thread overview]
Message-ID: <iluemf7ttts.fsf@atlas.pdc.kth.se> (raw)
In-Reply-To: Julian Assange's message of "07 Oct 1999 12:41:17 +1000"
Julian Assange <proff@q.org> writes:
> Has anyone considered writing a mail-indexing sql backend to replace
> nnml? I'm a *heavy* nnml user (8k groups, 15k messages in my personal
> mail folder etc) and unfortunately dealing with this morass is starting
> to show nnmls limitations.
Does profiling show that nnml is the bottleneck?
When I profiled it, nnml wasn't the biggest bottleneck so other things
should be optimized first. Like gnus-range-*.
next prev parent reply other threads:[~1999-10-07 9:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 2:41 Julian Assange
1999-10-07 9:15 ` Simon Josefsson [this message]
1999-10-07 10:52 ` Julian Assange
1999-11-06 18:23 ` Lars Magne Ingebrigtsen
1999-11-14 19:40 ` Greg Stark
1999-11-15 19:52 ` Lars Magne Ingebrigtsen
1999-11-15 20:03 ` Randal L. Schwartz
1999-11-15 20:06 ` Bruce Stephens
1999-11-15 20:34 ` Lars Magne Ingebrigtsen
1999-11-15 20:17 ` William M. Perry
1999-11-15 20:52 ` Randal L. Schwartz
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=iluemf7ttts.fsf@atlas.pdc.kth.se \
--to=jas@pdc.kth.se \
--cc=ding@gnus.org \
--cc=proff@iq.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).