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] Help with two small shared file servers
Date: Wed, 17 Aug 2011 14:00:38 -0700	[thread overview]
Message-ID: <20110817210038.66E0CB827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 17 Aug 2011 13:09:47 +0300." <CAEAzY3_Vx8WW1Oumt0t1_Ay6LtpTFFonpwMD+=0DYCM-yxXaeA@mail.gmail.com>

On Wed, 17 Aug 2011 13:09:47 +0300 =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= <aram.h@mgk.ro>  wrote:
> Hello,
>
> I'm looking for advice on how to build a small network of two file
> servers. I'm hoping most servers to be Plan9, clients are Windows and
> Mac OS X.
>
> I have 2 houses separated by about 40ms of network latency. I want to
> set some servers in each location and have all data accessible from
> anywhere. I'll have about 2TB of data at each location, one location
> will probably scale up.
	...
> Is 9p suitable for this? How will the 40ms latency affect 9p
> operation? (I have 100Mbit).

With a strict request/response protocol you will get no more
than 64KB once every 80ms so your throughput at best will be
6.55Mbps or about 15 times slower than using HTTP/FTP on
100Mbps link for large files.  [John, what was the link speed
for the tests in your thesis?]

> Right now (only one location) I am using a Solaris server with ZFS
> that serves SMB and iSCSI.

Using venti in place of (or over) ZFS on spinning disks would
incur further performance degradation.

> Any tips are welcomed :-),

Since you want everything accessble from both sites, how about
temporarily caching remote files locally?  There was a usenix
paper about `nache', a caching proxy for nfs4 that may be of
interest. Or may be ftpfs with a local cache if remote access
is readonly?



  parent reply	other threads:[~2011-08-17 21:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17 10:09 Aram Hăvărneanu
2011-08-17 14:11 ` Anthony Sorace
2011-08-17 14:32   ` John Floren
2011-08-17 15:39   ` erik quanstrom
     [not found]   ` <CAL4LZyiEk35Kfq_wezUaEvJWsYX3ONeordrD7sQjFr+45fQiWg@mail.gmail.c>
2011-08-18  5:34     ` erik quanstrom
2011-08-18  5:48       ` John Floren
     [not found]       ` <CAL4LZygoKQZoTvof4F_fBQhxqsQZb2r+FR_nkgf=YbU94WvoBQ@mail.gmail.c>
2011-08-18 13:26         ` erik quanstrom
2011-08-18 14:21           ` Lucio De Re
2011-08-19  8:15           ` cinap_lenrek
2011-08-17 21:00 ` Bakul Shah [this message]
2011-08-17 21:19   ` John Floren
2011-08-17 21:22   ` Skip Tavakkolian
2011-08-18  5:29   ` erik quanstrom
2011-08-18  5:47     ` Tristan Plumb
2011-08-18  6:25     ` Bakul Shah
2011-08-30 21:40 ` Ethan Grammatikidis
     [not found] <CAEAzY3_Vx8WW1Oumt0t1_Ay6LtpTFFonpwMD+=0DYCM-yxXaeA@mail.gmail.c>
2011-08-17 15:42 ` 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=20110817210038.66E0CB827@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).