9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: 9fans@9fans.net
Subject: Re: [9fans] Streaming on venti
Date: Thu,  5 Jun 2008 16:42:14 +0200	[thread overview]
Message-ID: <20080605144214.GA30375@nibiru.local> (raw)
In-Reply-To: <20080605140141.A17931E8C1F@holo.morphisms.net>

* 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 ?

> For a 1GB file, that means you have to load two extra blocks to find
> the first one, and 322 interior blocks to find all 131,072 data blocks.
> Is improving that 0.2% really your justification for a less capable
> data structure?

Well, I'll have to think about this. My primary goal is to
make the sequential read as fast as possible. There won't be
any non-sequential access.

> Venti's performance is dominated much more by fragmentation
> in where the blocks are laid out in the arena logs (that causes seeks)
> than anything in higher level data structures.  There is a paper about
> this in the upcoming Usenix.  See http://swtch.com/~rsc/papers/
> for a link to PDF and HTML.  (Because the paper is targeted at a
> non-Plan 9 audience, "Venti" in that paper refers to venti as described
> in the original paper.  The current venti sources implement all the
> improvements described as "Foundation" in the paper.)

thx, I'll have a look at this (as soon as time allows ;-o).


cu
--
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 cellphone: +49 174 7066481   email: info@metux.de   skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------



  reply	other threads:[~2008-06-05 14:42 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 [this message]
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

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=20080605144214.GA30375@nibiru.local \
    --to=weigelt@metux.de \
    --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).