From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fossil/venti memory allocation?
Date: Tue, 24 May 2005 03:47:30 +1000 [thread overview]
Message-ID: <775b8d190505231047207086d4@mail.gmail.com> (raw)
In-Reply-To: <9773.1116866132@piper.nectar.cs.cmu.edu>
there has been suggestions before (check the list and wiki).
i've found that being generous to fossil is a good thing and
make sure you have swap on for those little moments when
you, ahh, need a bit of swap.
brucee
On 5/24/05, Dave Eckhardt <davide+p9@cs.cmu.edu> wrote:
> Let's say I have a auth/fossil/venti server with
> 512 meg of RAM (430 meg free when everything
> is running with default configurations).
>
> Anybody want to suggest how I might allocate
> that among:
> * fossil block cache (open -c xxx)
> * venti block cache (mem xxx)
> * venti disk cache (bcmem xxx)
> * venti index cache (icmem xxx)
> * memory left over for cron, tftpd, etc.
>
> Dave Eckhardt
>
next prev parent reply other threads:[~2005-05-23 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 16:35 Dave Eckhardt
2005-05-23 17:47 ` Bruce Ellis [this message]
2005-05-24 3:02 ` Dave Eckhardt
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=775b8d190505231047207086d4@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@cse.psu.edu \
/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).