Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Comparing mail backends
Date: 24 Sep 1999 20:52:10 +0200	[thread overview]
Message-ID: <m3vh9016sl.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "22 Aug 1999 14:38:54 +0200"

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Each kind of mail backend has its own advantages and disadvantages.
> Here, I'd like to learn something about speed.
> 
> Which operations are particularly slow and which operations are
> particularly fast for the following backends?
> 
>   - nnmbox
>   - nnbabyl
>   - nnfolder
>   - nnmh
>   - nnml
> 
> Operations I'm thinking of:
> 
>   - Mail splitting.
>   - `B c' and `B m' within a server.
>   - Entering a group (ie, fetching headers).
>   - Searching in a group with `M-s'.
>   - Checking all groups when Gnus is started.  (I'm not sure what
>     happens here, but I think at least the number of unread messages
>     in each group needs to be computed.)
> 
> Feel free to add operations which I haven't thought of.
> 
> Of the above, I know nnml best, and I have seen a bit of nnfolder and
> nnmh.  But I don't know how nnfolder and nnml compare when moving
> messages between groups -- which one is faster?  I think fetching
> headers is fastest in nnml, then comes nnfolder, and then nnmh.  Is
> this correct?  nnmh seems to be very slow when Gnus is started, at
> least compared with nnml; but how does nnfolder come in?

Let's see...  This is just off the top of my head; I haven't done any
studies.  In order of speed, fastest first:

Mail splitting: nnmbox, nnbabyl, nnfolder, nnmh, nnml
Moving and copying: Er.

No, wait.  There's two kinds of speeds involved.  For instance, if you 
get one new mail, the overhead of loading the huge nnmbox mbox into
Emacs will be large, and nnmh will be fastest.  If you get a gazillion 
mails, nnmbox will still have to load its mbox, but after that, it'll
just append to its buffer, so it will be faster.

The same goes for pretty much all the other operations as well --
`M-s' in an nnfolder group is faster, but entering an nnml group is
faster than entering an nnfolder group.  And stuff.  Like.

Checking groups on startup is the same for all the mail backends
except nnmh, since they all have active files.

(And I do believe Quimby got, er, slashdotted.  I mean it only has
16MB of RAM, and each PHP-httpd takes 8MB.  Swap-o-rama.  And I
probably forgot to put a MaxClients thing into the startup file.

It had a load of 49 before it stopped talking to me.

Wait!  I got a prompt!  Yay!

I should put more RAM into the beast.)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  parent reply	other threads:[~1999-09-24 18:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-22 12:38 Kai Großjohann
1999-08-23  9:53 ` Searching a (mail) group Robert Bihlmeyer
1999-09-24 18:53   ` Lars Magne Ingebrigtsen
1999-09-24 18:52 ` Lars Magne Ingebrigtsen [this message]
1999-09-27 17:13   ` Comparing mail backends Wes Hardaker
1999-09-27 17:21     ` Lars Balker Rasmussen

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=m3vh9016sl.fsf@quimbies.gnus.org \
    --to=larsi@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).