9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] venti and "contrib": RFC
Date: Thu,  5 Jan 2012 16:31:00 -0500	[thread overview]
Message-ID: <c545915821ea5ec2215100513d6fb7f5@chula.quanstro.net> (raw)
In-Reply-To: <CAG3N4d8Jdazahj8EeECDAVpU2DBZqD3XR9FJk_6znCV1QL=Q-Q@mail.gmail.c>

On Thu Jan  5 16:24:58 EST 2012, yarikos@gmail.com wrote:
> 2012/1/5 Bakul Shah <bakul@bitblocks.com>:
> > You'd save a bunch of energy if you only powered up venti
> > disks once @ 4AM for a few minutes (and on demand when you
> > look at /n/dump).  Though venti might have fits! And the disks
> > might too! So may be this calls for a two level venti? First
> > to an SSD RAID and a much less frequent venti/copy to hard
> > disks.
> 
> I think you're confusing kenfs+worm with fossil+venti in sense that
> ken fs is a complete cache for worm while fossil is a write cache for
> venti. You need venti running all the time.

this only could work if you assume that everything in the worm
is also in the cache, and you've configured your cache to cache the worm.
since these days the cache is often similar in performance to the worm, the
default we use is to not copy the worm into the cache.  this would just
result in more i/o.

so tl;dr you need the worm available at all times be it venti+fossil
or ken fs/cwfs

- erik



  parent reply	other threads:[~2012-01-05 21:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 12:48 tlaronde
2012-01-05 12:59 ` erik quanstrom
2012-01-05 13:20   ` tlaronde
2012-01-05 13:27     ` erik quanstrom
2012-01-05 13:40       ` tlaronde
2012-01-05 14:14         ` erik quanstrom
2012-01-05 15:10           ` tlaronde
2012-01-05 13:28     ` tlaronde
2012-01-05 14:15       ` erik quanstrom
2012-01-05 13:48 ` David du Colombier
2012-01-05 15:15   ` tlaronde
2012-01-05 15:44     ` Russ Cox
2012-01-05 16:39       ` tlaronde
2012-01-05 17:03         ` David du Colombier
2012-01-05 17:36           ` ron minnich
2012-01-05 18:17             ` tlaronde
2012-01-05 17:51         ` Bakul Shah
2012-01-05 18:01           ` erik quanstrom
2012-01-05 18:25             ` Bakul Shah
2012-01-05 18:43               ` erik quanstrom
2012-01-05 19:56                 ` Bakul Shah
2012-01-05 23:08             ` Aram Hăvărneanu
     [not found]     ` <CADSkJJXMBGnjtXbL5w+WMuxVbnW_+D6hQXYMN04wzYu+yXaCzA@mail.gmail.c>
2012-01-05 18:07       ` John Floren
2012-01-05 18:19         ` tlaronde
2012-01-05 18:48         ` Bakul Shah
2012-01-05 18:50           ` erik quanstrom
2012-01-05 19:13             ` Aram Hăvărneanu
     [not found]             ` <CAEAzY3-7w24ZJm7J08MGv98x7xjzZffFoNJvoeMSNM1FqtrEVw@mail.gmail.c>
2012-01-05 19:17               ` erik quanstrom
2012-01-05 19:57             ` Bakul Shah
2012-01-05 20:03               ` erik quanstrom
2012-01-08  1:29                 ` Bakul Shah
2012-01-05 18:53           ` John Floren
2012-01-05 19:40             ` ron minnich
2012-01-05 21:12           ` Steve Simon
2012-01-05 21:24           ` Yaroslav
     [not found]           ` <CAG3N4d8Jdazahj8EeECDAVpU2DBZqD3XR9FJk_6znCV1QL=Q-Q@mail.gmail.c>
2012-01-05 21:31             ` erik quanstrom [this message]
2012-01-05 19:45         ` 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=c545915821ea5ec2215100513d6fb7f5@chula.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).