From: "erik quanstrom" <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, "C H Forsyth" <forsyth@vitanuova.com>
Subject: Re: [9fans] Scaleable mail repositories.
Date: Mon, 31 Oct 2005 06:32:13 -0600 [thread overview]
Message-ID: <20051031123213.0E9A51AE726@dexter-peak.quanstro.net> (raw)
In-Reply-To: <fb4bdae61898eb36d87df9ce1df0563a@vitanuova.com>
on the other hand, what is the downside of keeping one message
per file? the upside is that no indexing is required.
- erik
C H Forsyth <forsyth@vitanuova.com> writes
|
| --upas-vddxtudmbktypqdrugeyxvxyrl
|
| i don't understand why, now that it's easy to write file servers
| (compared to unix days), it's necessary to store the mail messages
| as actual separate files or directories. the main problem with
| upas/fs i find is that it rewrites the file instead of treating it
| as append-only, and it reads the whole thing into memory (in a moderately
| bulky format); rather than maintaining a separate index file or files,
| and loading as needed. both the storage and index structure can
| then be made suitable for the task.
next prev parent reply other threads:[~2005-10-31 12:32 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 15:34 [9fans] rfork(RFPROC) and ffork() erik quanstrom
2005-10-29 19:11 ` William Josephson
2005-10-29 19:18 ` Russ Cox
2005-10-29 23:00 ` erik quanstrom
2005-10-29 23:24 ` Francisco J Ballesteros
2005-10-29 23:38 ` Russ Cox
2005-10-30 0:19 ` erik quanstrom
2005-10-30 1:07 ` Russ Cox
2005-10-30 1:15 ` Ronald G Minnich
2005-10-30 1:22 ` geoff
2005-10-30 1:58 ` jmk
2005-10-30 1:54 ` Dave Eckhardt
2005-10-30 2:24 ` erik quanstrom
2005-10-30 2:51 ` geoff
2005-10-30 1:10 ` geoff
2005-10-30 1:18 ` Paul Lalonde
2005-10-30 6:52 ` Skip Tavakkolian
2005-10-30 10:14 ` Francisco J Ballesteros
2005-10-30 15:17 ` Russ Cox
2005-10-30 23:00 ` Dave Eckhardt
2005-10-30 23:14 ` George Michaelson
2005-10-31 2:15 ` erik quanstrom
2005-10-31 2:33 ` geoff
2005-10-31 3:23 ` Skip Tavakkolian
2005-10-31 4:20 ` Lyndon Nerenberg
2005-10-31 21:31 ` Dave Eckhardt
2005-10-31 4:06 ` [9fans] Scaleable mail repositories Lyndon Nerenberg
2005-10-31 10:55 ` C H Forsyth
2005-10-31 12:32 ` erik quanstrom [this message]
2005-11-01 19:56 ` rog
2005-11-01 22:29 ` Francisco J Ballesteros
2005-11-08 19:56 ` rog
2005-11-08 23:22 ` Joel Salomon
2005-11-09 0:51 ` Caerwyn Jones
2005-11-09 0:55 ` Russ Cox
2005-11-09 3:32 ` erik quanstrom
2005-10-31 15:30 ` jmk
2005-10-30 1:10 ` [9fans] rfork(RFPROC) and ffork() William Josephson
2005-10-31 14:48 ` Russ Cox
2005-10-31 11:32 [9fans] Scaleable mail repositories Fco. J. Ballesteros
2005-10-31 16:01 ` Ronald G Minnich
2005-10-31 15:06 ` jmk
2005-10-31 15:14 Fco. J. Ballesteros
2005-10-31 16:22 ` Ronald G Minnich
2005-10-31 18:37 ` William Josephson
2005-10-31 15:19 Fco. J. Ballesteros
2005-10-31 15:33 Fco. J. Ballesteros
2005-10-31 18:38 ` William Josephson
2005-11-09 9:45 Fco. J. Ballesteros
2005-11-09 10:24 ` Charles Forsyth
2005-11-09 14:19 ` Sam
2005-11-10 1:24 ` erik quanstrom
2005-11-10 2:30 ` Russ Cox
2005-11-10 6:33 ` Scott Schwartz
2005-11-10 11:55 ` erik quanstrom
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=20051031123213.0E9A51AE726@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=forsyth@vitanuova.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).