Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: [PATCH] Mail fetching on memory-poor machines
Date: 14 Jul 1999 21:21:00 -0400	[thread overview]
Message-ID: <m3pv1u4sjn.fsf@peorth.gweep.net> (raw)
In-Reply-To: Jim Pick's message of "14 Jul 1999 14:31:35 -0700"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Jim Pick <jim@jimpick.com>  on Wed, 14 Jul 1999
| Why not fix the problem?  The results of the problem are so bad that
| it's basically a bug.  Fixing it seems like a more logical thing to
| do, rather than force everybody to use the program in a certain way.

Because, if I understand what your code does (which might not be the case),
it only works for people who use Gnus "your" way while slowing it down
unnecessarilly for those who are not on memory-starved systems, have large
nnfolders, and do use Gnus to split mail sources.

Personally, I am all for lean and mean, which is one of the reasons why I
don't use nnfolder.  I tried it, briefly, back when I was on a 12MB system.
That was a mistake :).

For what its worth, inode starvation is not as likely as you might think.
The average mail message is ~3-4kB; the average inode size on a modern
filesystem is 4kB.  One message, one inode.  On an ~1GB filesystem you will
have around 256k inodes (more, actually).  In practical terms, you will run
out of space before you run out of inodes, unless your filesystem is tuned
with unusually large inodes or you are suffering under a woefully
restrictive inode quota.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.8 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE3jTd8gl+vIlSVSNkRAq8ZAJ9qy2roxy7JgfnhUDNZrU3sFnnlbwCgz/KX
tFqSmLkn2MR74Xjc8PIa/uw=
=Bsku
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@peorth.gweep.net>    \ Warning: pregnant women, the elderly, and
Minion of Nathan - Nathan says Hi! \ children under 10 should avoid prolonged
PGP Key: at a key server near you!  \ exposure to Happy Fun Ball.


  reply	other threads:[~1999-07-15  1:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-14  5:13 Jim Pick
1999-07-14 19:02 ` Stainless Steel Rat
1999-07-14 21:31   ` Jim Pick
1999-07-15  1:21     ` Stainless Steel Rat [this message]
1999-07-15  3:23       ` Jim Pick
1999-07-15 14:44         ` Stainless Steel Rat

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=m3pv1u4sjn.fsf@peorth.gweep.net \
    --to=ratinox@peorth.gweep.net \
    /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).