From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: overview file access when spooling and nnml/nnimap performance
Date: 22 Sep 1999 19:08:37 +0200 [thread overview]
Message-ID: <iluyadynaay.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Hannu Koivisto's message of "22 Sep 1999 18:58:28 +0300"
Hannu Koivisto <azure@iki.fi> writes:
> 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.
I don't know much about how the spooling phase works, but I would
assume it involves calculating (especially expanding/compacting) gnus
"ranges". And the gnus-range-* functions do very poorly when more
than, say, 10.000 articles are involved.
Try M-x elp-instrument-package RET gnus RET, fetch new mail, and look
at M-x elp-results RET, if gnus-range-* comes up at the top you've
confirmed my guess. If not, you should be able to figure out where all
the time is spent, no?
next prev parent reply other threads:[~1999-09-22 17:08 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
1999-09-22 16:17 ` Kai Großjohann
1999-09-22 17:08 ` Simon Josefsson [this message]
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=iluyadynaay.fsf@badis.pdc.kth.se \
--to=jas@pdc.kth.se \
--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).