From: "Steve Simon" <steve@quintile.net>
To: csant@csant.info, 9fans@cse.psu.edu
Subject: Re: [9fans] Sensible fossil+venti partitioning
Date: Wed, 12 Jul 2006 21:07:16 +0100 [thread overview]
Message-ID: <13627d93c2587e4b5e42edda1e8f67b5@quintile.net> (raw)
In-Reply-To: <op.tclbe3jwd84skq@fiore.malebolge>
Fossil needs to be big enough for all the changes you are likely
to do between venti snapshots.
Given venti usually snapshots every night I would say a fossil of
between 2 and 4 Gb is enough for most people.
You will want a swap of 1Gb or so, a 9fat of 100Mb, a sector
for nvram and perhaps another for fsconfig
(if you are mirroring or striping).
Give the remainder to Venti - about 5% to index and 95% to the arena.
These are my rules fo thumb, however others may disagree (ducks).
-Steve
next prev parent reply other threads:[~2006-07-12 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 19:07 csant
2006-07-12 20:07 ` Steve Simon [this message]
2006-07-12 21:14 ` csant
2006-07-12 22:30 ` Steve Simon
2006-07-13 14:51 ` Richard Miller
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=13627d93c2587e4b5e42edda1e8f67b5@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.edu \
--cc=csant@csant.info \
/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).