From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Question about fossil
Date: Sun, 8 Jun 2014 04:04:39 -0400 [thread overview]
Message-ID: <68678ded498cd0447f0d7c9884325dc9@brasstown.quanstro.net> (raw)
In-Reply-To: <CAGMcHPqw3zjqRLofWbZE2eA1wsfLZ4=DDWWtYFm3SHK8N1y+Lw@mail.gmail.com>
> I wasn't thinking "I would need a big venti", more "I only need a small
> fossil". My train of thought was because the fossil size is used to store
> the unarchived files after which they can be gotten from venti that it
> might be practical to only have the fossil be big enough to store the
> maximal size of files that will change per day(snapshot interval).
>
> I would struggle to change 16GB a day unless I'm backing up a VM so 64
> seemed like it should accommodate any changes and still leave room for lots
> of often used files to be kept there (if fossil thinks like that).
why bother optimizing this? fossil is going to be <1% of the disk even
if you make it silly huge.
- erik
next prev parent reply other threads:[~2014-06-08 8:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 20:39 Riddler
2014-06-07 23:17 ` Steve Simon
2014-06-07 23:49 ` Riddler
2014-06-08 8:04 ` erik quanstrom [this message]
2014-06-09 20:25 ` Riddler
2014-06-08 8:30 ` Steve Simon
2014-06-08 8:39 ` erik quanstrom
2014-06-08 7:03 ` Bakul Shah
2014-06-08 7:56 ` erik quanstrom
2014-06-08 16:56 ` Bakul Shah
2014-06-08 17:06 ` erik quanstrom
2014-06-10 10:59 ` Nicolas Bercher
2014-06-09 20:21 ` Riddler
2014-06-09 21:12 ` Lyndon Nerenberg
2014-06-09 21:25 ` erik quanstrom
2014-06-09 21:52 ` Bakul Shah
2014-06-09 22:22 ` erik quanstrom
2014-06-09 22:36 ` Bakul Shah
2014-06-10 0:15 ` Brian L. Stuart
2014-06-10 4:24 ` Bakul Shah
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=68678ded498cd0447f0d7c9884325dc9@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).