From: Thomas Neumann <blacky_tn@gmx.de>
Subject: Re: Questions on nnmaildir
Date: Mon, 31 Mar 2003 18:23:04 +0200 [thread overview]
Message-ID: <87llyvjyjb.fsf@papa-san.t-net.theredguy.de> (raw)
In-Reply-To: <87isu0gvs2.fsf@mail.paradoxical.net> (Josh Huber's message of "Sun, 30 Mar 2003 20:38:37 -0500")
Josh Huber <huber@alum.wpi.edu> writes:
> Thomas Neumann <blacky_tn@gmx.de> writes:
>
>> But that's not the reason, why I write this mail. It seems that
>> nnmaildir is quite an inode-hogger.
> They're hardlinks.
Hmm.
Output of `df -i`
1) /dev/hda5 611648 61281 550367 11% /home
2) /dev/hda5 611648 61297 550351 11% /home
3) /dev/hda5 611648 61302 550346 11% /home
4) /dev/hda5 611648 61419 550229 11% /home
5) /dev/hda5 611648 61548 550100 11% /home
1) nothing done so far
2) B c message to new maildir group.test, which did not exist so far
3) B c different message to maildir group.test
4) C-u 50 # B c nnmaildir+thomas:group.Inbox
(group.Inbox didn't exist before)
5) Copy 50 other mails to group.Inbox
Seems like I have about 250K mails left before I run out of Inodes on
/home. Which is not as bad as it looked first, but still less then I
expected.
Is it really that much faster for nnmaildir to pick a specific nov-file
and grab its contents then to search through a single file containing
all novs and look for a match? [Or what's the reason behind doing it
this way?]
tschüß
thomas
next prev parent reply other threads:[~2003-03-31 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-30 22:16 Thomas Neumann
2003-03-31 1:38 ` Josh Huber
2003-03-31 16:23 ` Thomas Neumann [this message]
2003-03-31 14:22 ` Kai Großjohann
2003-04-02 17:33 Paul Jarc
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=87llyvjyjb.fsf@papa-san.t-net.theredguy.de \
--to=blacky_tn@gmx.de \
/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).