From: Hannu Koivisto <azure@iki.fi>
Subject: Re: overview file access when spooling and nnml/nnimap performance
Date: 22 Sep 1999 18:58:28 +0300 [thread overview]
Message-ID: <87aeqfuee3.fsf@senstation.vvf.fi> (raw)
In-Reply-To: Simon Josefsson's message of "22 Sep 1999 16:54:29 +0200"
Simon Josefsson <jas@pdc.kth.se> writes:
| If you want numbers, entering a large group (~1000 articles) with
| nnimap spend 20 % of the time in nnimap and 80 % in Gnus. For nnml
| theese numbers are 1 % / 99 %.
|
| This indicate that if you want better performance, you should spend
| your time optimizing Gnus instead of working on a backend. The
Hm, right, thanks for the numbers. However, perhaps I was a bit
unclear but I never meant that backend would improve group access
at least dramatically; I do agree with you that it's Gnus' problem
(I think I said it was Elisp's problem, but Gnus _and_ Elisp is
actually what I was thinking). The primary reason why I was
thinking about backend was the spooling phase. That's the primary
problem I'm seeing now -- it has slowed down a lot while my folders
have grown larger and I don't think Gnus needs to do anything that
would prevent scaling in this case. Perhaps I'm wrong, but this is
what I'm trying to find out.
--
Hannu
next prev parent reply other threads:[~1999-09-22 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-22 13:48 Hannu Koivisto
1999-09-22 14:13 ` Kai Großjohann
1999-09-22 15:32 ` Hannu Koivisto
1999-09-22 15:50 ` Kai Großjohann
1999-09-22 17:00 ` Simon Josefsson
1999-09-22 16:52 ` Simon Josefsson
1999-09-22 14:54 ` Simon Josefsson
1999-09-22 15:58 ` Hannu Koivisto [this message]
1999-09-22 16:17 ` Kai Großjohann
1999-09-22 17:08 ` Simon Josefsson
1999-09-22 18:15 ` Hannu Koivisto
1999-10-04 10:27 ` Robert Bihlmeyer
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=87aeqfuee3.fsf@senstation.vvf.fi \
--to=azure@iki.fi \
/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).