From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Interested in improving networking in Plan 9
Date: Sun, 30 Aug 2009 13:53:20 -0400 [thread overview]
Message-ID: <89c5d8771b3e1fafe5b2102ce5f8bb4f@quanstro.net> (raw)
In-Reply-To: <f75780240908301040w3720122gc3d6a37d483035f@mail.gmail.com>
> Try this - build the source to charon over a 200ms link over 9p. Then
> try again over sshfs.
why would you do this? why not run the compile closer to
the source. this is the power of plan 9.
> Also, look at a single terminal with a local fossil install. Trace the
> path of an 'ls /'. Count the number of copies and context switches.
>
> Having the fastest file server in the world means nothing for file
> system performance when your path to it is a maze of twisty passages,
> all alike.
again, this is not a typical install for a performance-sensitive
system. and i don't know that anyone ever claimed fossil
to be a high-performance file system. running a file system in user
space is a matter of convienence, not performance.
at coraid, we run a stand-alone ken's file server. ken's file
server has no user space. so while there are context switches,
those are really speedy. they take maybe a few hundred cycles.
the real win is that no data is copied from/to user space and
there is one global page table that is never changed. there are
no tlb flushes. those can hurt.
before the switch to nupas, we averaged 200MB/s of fileserver traffic
during the day to >50 clients on a single, fairly pedestrian
xeon 5000 machine with 3.5gb of usable memory.
perhaps my standards are low and i'm out of touch, but i don't
think nfs could do that well with that little.
- erik
next prev parent reply other threads:[~2009-08-30 17:53 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 7:21 Vinu Rajashekhar
2009-08-30 14:21 ` ron minnich
2009-08-30 16:19 ` Eric Van Hensbergen
2009-08-30 17:07 ` erik quanstrom
2009-08-30 17:40 ` Venkatesh Srinivas
2009-08-30 17:53 ` erik quanstrom [this message]
[not found] ` <c81a07350908300842w3df8321aidf55096b65eb9b77@mail.gmail.com>
2009-08-30 18:17 ` ron minnich
2009-08-30 18:35 ` ron minnich
2009-08-31 3:34 ` erik quanstrom
2009-08-31 12:45 ` Eric Van Hensbergen
2009-08-31 12:51 ` erik quanstrom
2009-08-31 12:59 ` Vinu Rajashekhar
2009-08-31 13:05 ` erik quanstrom
2009-08-31 13:48 ` Anthony Sorace
2009-08-31 14:51 ` Devon H. O'Dell
2009-08-31 15:03 ` Vinu Rajashekhar
2009-08-31 13:42 ` Eric Van Hensbergen
2009-08-31 14:04 ` erik quanstrom
2009-08-31 14:25 ` Eric Van Hensbergen
2009-08-31 14:36 ` erik quanstrom
2009-08-31 14:57 ` Eric Van Hensbergen
2009-08-31 15:52 ` erik quanstrom
2009-08-31 16:12 ` Eric Van Hensbergen
2009-08-31 14:55 ` Francisco J Ballesteros
2009-08-31 15:09 ` Eric Van Hensbergen
2009-08-31 15:56 ` erik quanstrom
2009-08-31 16:16 ` Bakul Shah
2009-08-31 16:33 ` Eric Van Hensbergen
2009-09-02 16:50 ` Bakul Shah
2009-09-02 17:10 ` Robert Raschke
2009-09-03 11:21 ` matt
2009-09-03 12:50 ` erik quanstrom
2009-09-03 16:13 ` Anthony Sorace
2009-09-03 16:29 ` erik quanstrom
2009-09-03 16:34 ` Robert Raschke
2009-09-03 21:50 ` Daniel Lyons
2009-09-03 19:08 ` Steve Simon
2009-08-31 17:09 ` Devon H. O'Dell
2009-08-31 17:20 ` erik quanstrom
2009-08-31 17:32 ` Devon H. O'Dell
2009-08-31 18:00 ` erik quanstrom
2009-08-31 4:17 ` Federico G. Benavento
2009-08-31 4:53 ` Vinu Rajashekhar
2009-08-30 17:22 erik quanstrom
2009-08-30 17:36 ` Vinu Rajashekhar
2009-08-30 17:56 ` 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=89c5d8771b3e1fafe5b2102ce5f8bb4f@quanstro.net \
--to=quanstro@quanstro.net \
--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).