9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] file server speed
Date: Thu, 17 Jul 2014 12:26:43 -0700	[thread overview]
Message-ID: <20140717192643.113D7B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 17 Jul 2014 15:10:34 EDT." <fd1c3cf7f156332dcd23891262f87059@ladd.quanstro.net>

On Thu, 17 Jul 2014 15:10:34 EDT erik quanstrom <quanstro@quanstro.net> wrote:
> > So long as a server returns a block corresponding to its SHA1
> > score, you (the client) don't care whether it is the same
> > server you wrote the original block to or another (and you can
> > always verify the returned block). This opens up some
>
> but this isn't unique to content-addressed storage.  as long
> as the block contents are the same, normal block storage can
> be served from anywhere.

But this is a much stricter requirement for normal block
storage (every replica has to have the same content for a
given block number N and if you have disks of different sizes,
you either waste storage or have to add another mapping
layer). With CAS you have much more freedom.

> > interesting choices. For instance, you can multicast each read
> > or write or you can set up a hierarchy of servers and switch
> > to another one (or even get different blocks from different
> > instances). How the writes are handled/replicated.stored is
> > entirely upto the server (cluster).  Or you can implement a
> > bittorrent like facility on top of venti (I call it bitventi
> > or b20).
>
> why not distributed hashing?  distributed hashes have existing
> fast implementations.  venti does not.

You can change implementations.  Russ's "ventino" and Lucho's
govt's "vtmm" server use different storage schemes from
plan9's venti server.

I am just playing with this stuff but if you want clustered,
distributed storage you'd probably need some server side
protocol to manage storage sanely. And add more complications
if you want to improve performance.



  reply	other threads:[~2014-07-17 19:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  6:13 kokamoto
2014-07-15 13:02 ` Anthony Sorace
2014-07-15 16:30 ` cinap_lenrek
2014-07-15 16:56   ` erik quanstrom
2014-07-16  0:04   ` kokamoto
2014-07-16  0:36     ` kokamoto
2014-07-16 17:26       ` erik quanstrom
2014-07-16 14:23     ` Steven Stallion
2014-07-16 14:53       ` Ramakrishnan Muthukrishnan
2014-07-17  1:13         ` Steven Stallion
2014-07-17 17:13           ` Ramakrishnan Muthukrishnan
2014-07-17 21:44         ` cam
2014-07-16 17:41       ` erik quanstrom
2014-07-16 23:15       ` kokamoto
2014-07-17  0:29         ` Steven Stallion
2014-07-17  0:31           ` Steven Stallion
2014-07-17  1:10             ` john francis lee
2014-07-17  1:09           ` john francis lee
2014-07-17  1:10           ` Bakul Shah
2014-07-17 16:56           ` erik quanstrom
2014-07-17 18:14             ` Bakul Shah
2014-07-17 18:39               ` erik quanstrom
2014-07-17 19:01               ` Bakul Shah
2014-07-17 19:10                 ` erik quanstrom
2014-07-17 19:26                   ` Bakul Shah [this message]
2014-07-16 17:23     ` erik quanstrom
2014-07-16 23:01       ` kokamoto
2014-07-17 17:03         ` erik quanstrom
2014-07-18 16:50           ` hiro
2014-07-18 19:36             ` erik quanstrom
2014-07-18 20:11               ` 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=20140717192643.113D7B827@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --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).