From: "ron minnich" <rminnich@gmail.com>
To: weigelt@metux.de,
"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Streaming on venti
Date: Fri, 6 Jun 2008 18:23:14 -0700 [thread overview]
Message-ID: <13426df10806061823n288c021flc39025a4ee821c15@mail.gmail.com> (raw)
In-Reply-To: <20080605144214.GA30375@nibiru.local>
On Thu, Jun 5, 2008 at 7:42 AM, Enrico Weigelt <weigelt@metux.de> wrote:
> * Russ Cox <rsc@swtch.com> wrote:
>> > VAC eg. is good for archiving, but it's tree-based structure
>> > is probably not optimal for streaming (on large files, a lot
>> > of blocks IMHO have to be loaded before getting the first
>> > payload block can be reached).
>>
>> A typical venti tree has a branching factor of 409 (8192/20).
>
> I gues, 8k is vac's index block size ?
> So, maybe it could even be improved (for my case) by increasing
> it to the 56k venti limit ?
As Russ makes pretty clear, this stuff all involves numbers that can
be reasoned about. Storage companies do such reasoning as their daily
bread.
So, rather than say stuff like "as fast as possible" (which is without
meaning) why not attach some numbers to this kind of speculation?
ron
prev parent reply other threads:[~2008-06-07 1:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 11:24 Enrico Weigelt
2008-06-05 12:19 ` ron minnich
2008-06-05 13:38 ` Enrico Weigelt
2008-06-05 13:47 ` erik quanstrom
2008-06-05 14:01 ` Russ Cox
2008-06-05 14:42 ` Enrico Weigelt
2008-06-05 15:40 ` Wilhelm B. Kloke
2008-06-05 15:57 ` erik quanstrom
2008-06-06 8:33 ` Wilhelm B. Kloke
2008-06-06 8:40 ` Francisco J Ballesteros
2008-06-06 9:44 ` Wilhelm B. Kloke
2008-06-06 12:59 ` erik quanstrom
2008-06-06 12:08 ` erik quanstrom
2008-06-06 13:16 ` Wilhelm B. Kloke
2008-06-06 14:06 ` erik quanstrom
2008-06-06 15:53 ` Russ Cox
2008-06-09 8:51 ` Wilhelm B. Kloke
2008-06-10 1:56 ` ron minnich
2008-06-10 2:38 ` erik quanstrom
2008-06-07 1:23 ` ron minnich [this message]
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=13426df10806061823n288c021flc39025a4ee821c15@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@9fans.net \
--cc=weigelt@metux.de \
/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).