Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: hildjj@fuentez.com, ding@ifi.uio.no
Subject: Re: Gnus5, procmail, and reading mail lists.
Date: Wed, 15 Nov 1995 15:32:01 +0100	[thread overview]
Message-ID: <199511151432.PAA20711@ssv4.dina.kvl.dk> (raw)
In-Reply-To: Sudish Joseph's message of 14 Nov 1995 23:37:13 -0500


The speed of Gnus mail splitting with nnml/nnmh is almost solely
depending on what file system you use.  I have used Gnus mail
splitting with three different file systems:

NFS: Incredible slow.  You can read each split message in the
minibuffer several times, take a sip of your tea, and speculate about
the possible content before the next message arrives.

Linux ext2fs: Incredible fast.  You can see some flimmer in the
message area, but haven't a chance to see what they are about.  I get
the impression that the speed of mail splitting on Linux is limited by
how fast it can print those messages on the screen.

BSD-FFS: Somewhere in between.  You can read the messages if you stay
alert.

The reason is probably that NFS is write through, and that BSD-FFS
directory content is write through, while Linux ext2fs buffers
everything. 

Conclusions:

1. LINUX R00LZ!

   (but set nnmail-delete-incoming to nil, just in case...)

2. There is really nothing Lars can do to speed up mail splitting. 

3. Using procmail to split mail	instead of Gnus doesn't speed up
   anything, unless you deliver directly into the folders instead 
   spool files.

4. If you don't run Linux, consider using nnfolder instead of nnml.

5. Consider reading mail on the NFS server instead of a client.

6. Consider buying PrestoServe(TM) for your NFS server.


  reply	other threads:[~1995-11-15 14:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-14  1:43 Steven L. Baur
1995-11-14 13:04 ` Per Abrahamsen
1995-11-15  2:42   ` Steven L. Baur
1995-11-14 16:27 ` Joe Hildebrand
1995-11-14 17:22   ` Scott Blachowicz
1995-11-14 21:35     ` Joe Hildebrand
1995-11-15  6:58     ` Sudish Joseph
1995-11-15 18:46       ` Scott Blachowicz
1995-11-15  4:37   ` Sudish Joseph
1995-11-15 14:32     ` Per Abrahamsen [this message]
1995-11-15 15:50       ` Kai Grossjohann
1995-11-15 16:13         ` Per Abrahamsen
1995-11-15 17:50         ` Steven L. Baur
1995-11-17 21:18   ` Jason L Tibbitts III
1995-11-17 21:40     ` Joe Hildebrand
  -- strict thread matches above, loose matches on Subject: below --
1995-11-14  1:55 Steven L. Baur
1995-11-13 22:21 Steven L. Baur
1995-11-13 20:33 Steven L. Baur
1995-11-13 22:43 ` Joe Hildebrand
1995-11-14 19:52   ` Edward J. Sabol
1995-11-13 17:48 Mark Borges
1995-11-13 20:16 ` Joe Hildebrand
1995-11-14  0:24   ` Mark Borges
1995-11-15  6:19 ` Mark Borges
1995-11-15  8:17   ` Steven L. Baur

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=199511151432.PAA20711@ssv4.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    --cc=ding@ifi.uio.no \
    --cc=hildjj@fuentez.com \
    /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).