From mboxrd@z Thu Jan 1 00:00:00 1970 From: "erik quanstrom" To: 9fans@cse.psu.edu, "C H Forsyth" References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: Subject: Re: [9fans] Scaleable mail repositories. Message-Id: <20051031123213.0E9A51AE726@dexter-peak.quanstro.net> Date: Mon, 31 Oct 2005 06:32:13 -0600 Cc: Topicbox-Message-UUID: a3267db2-ead0-11e9-9d60-3106f5b1d025 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 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.