All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Rick Peralta <fbp@tiac.net>, Project Hail <hail-devel@vger.kernel.org>
Subject: Re: HAIL volunteer Rick Peralta
Date: Wed, 29 Jul 2009 14:30:37 -0400	[thread overview]
Message-ID: <4A70954D.9000300@garzik.org> (raw)
In-Reply-To: <20090729121935.0e2d6f00.zaitcev@redhat.com>

Pete Zaitcev wrote:
> On Wed, 29 Jul 2009 13:59:28 -0400, Jeff Garzik <jeff@garzik.org> wrote:
> 
>> My point was more that there are real world situations where multiple 
>> outgoing streams from the client is significantly slower than a single 
>> stream into the cloud, plus asking the cloud to perform further copies.
> 
> We aren't exposing Chunk to clients outside the cloud, at least at present.
> Let's wait and see if applications exist that require it, and how they
> compete, say, with a bunch of NFS servers. The biggest difference about
> Chunk is its ability to plug into CLD. Drop that and it's not that
> special. But you can only use CLD if you are inside the cloud; in fact
> it works best when you're inside the same data center with the CLD cell.
> So I don't see the bandwidth argument having much weight.
> 
> I'm going to remember Fabian's idea of 3-rd party transfers, of course.
> That potentially offers a significant reduction of load on tabled.
> But mythical outside clients of Chunk are yet to be demostrated.

Note that "mythical outside clients" is a key design element in NFS 
v4.1, which is a parallel distributed filesystem technology.  chunkd 
clients are quite a bit different from CLD clients.

Similarly, Hadoop DFS, CloudStore and GoogleFS clients [analagously] 
talk directly to chunkd rather than going through tabled.

	Jeff




  reply	other threads:[~2009-07-29 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29025029.1248785350151.JavaMail.root@mswamui-andean.atl.sa.earthlink.net>
     [not found] ` <4A6F5A3E.1070907@garzik.org>
     [not found]   ` <4A704376.6000303@tiac.net>
2009-07-29 14:31     ` HAIL volunteer Rick Peralta Jeff Garzik
2009-07-29 16:52       ` Pete Zaitcev
2009-07-29 16:58         ` Fabian Deutsch
2009-07-29 17:17         ` Jeff Garzik
2009-07-29 17:59           ` Jeff Garzik
2009-07-29 18:19             ` Pete Zaitcev
2009-07-29 18:30               ` Jeff Garzik [this message]
2009-07-29 18:35             ` Fabian Deutsch
2009-07-29 19:14               ` Jeff Garzik
2009-07-31 16:37 Rick Peralta

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=4A70954D.9000300@garzik.org \
    --to=jeff@garzik.org \
    --cc=fbp@tiac.net \
    --cc=hail-devel@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.