From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] 9P optimization
Date: Sun, 24 Jun 2007 14:16:32 +1000 [thread overview]
Message-ID: <775b8d190706232116u43d53d7bl71d0267a1b246be3@mail.gmail.com> (raw)
In-Reply-To: <20070623200857.H1471@orthanc.ca>
rangbooming has lead to extreme optimiazations. i'll let skip
comment on it (he's asleep i guess). but i couldn't have much
worse RTT (sydney-seattle), and the traffic seems a lot lower now,
and the latency has improved extraordinarily.
brucee
On 6/24/07, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
> > The problem with cfs is that you still suffer the RPC to check for validity.
> > With 100ms of RTT, count 5 and you have a second. Also, for synthesized
> > files,
> > the cache does not save you from doing a walk, open, read.
>
> I'll be accused of being a heretic, but let me claim that much of the
> design of IMAP is geared towards avoiding those RTTs for that very reason.
> A good IMAP client wins by doing intelligent cacheing, and it gets there
> by using the subtle aspects of the protocol that accomodate that.
>
> Much as people slag the protocol, it does work well over slow (high
> latency) links, given a client that understands the protocol (sadly, most
> don't).
>
> I'm very curious about the efficiency of cfs, but my P9 environment
> doesn't have a remote terminal. It would be interesting to instrument cfs
> and collect some stats on the protocol behaviour behind the cache ...
>
> --lyndon
>
next prev parent reply other threads:[~2007-06-24 4:16 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 20:11 [9fans] About 9P Philippe Anel
2007-06-20 0:37 ` Russ Cox
2007-06-20 2:06 ` Roman Shaposhnick
2007-06-20 11:29 ` Anthony Sorace
2007-06-22 0:32 ` Derek Fawcus
2007-06-22 6:58 ` Philippe Anel
2007-06-22 15:57 ` Derek Fawcus
2007-06-22 20:32 ` Philippe Anel
2007-06-22 21:10 ` David Leimbach
2007-06-22 21:35 ` Philippe Anel
2007-06-22 21:46 ` David Leimbach
2007-06-22 21:55 ` Philippe Anel
2007-06-22 22:25 ` Philippe Anel
2007-06-22 22:57 ` David Leimbach
2007-06-22 23:01 ` Anant Narayanan
2007-06-23 4:30 ` Russ Cox
2007-06-23 5:10 ` Skip Tavakkolian
2007-06-23 9:25 ` Francisco J Ballesteros
2007-06-23 15:50 ` Martin Atkins
2007-06-23 6:24 ` Philippe Anel
2007-06-23 15:00 ` Rob Pike
2007-06-24 0:52 ` [9fans] 9P optimization Lyndon Nerenberg
2007-06-24 3:04 ` Francisco J Ballesteros
2007-06-24 3:15 ` Lyndon Nerenberg
2007-06-24 4:08 ` ron minnich
2007-06-24 9:34 ` Steve Simon
2007-06-24 10:06 ` Lyndon Nerenberg
2007-06-24 11:38 ` Steve Simon
2007-06-24 13:34 ` Lyndon Nerenberg
2007-06-25 0:34 ` ron minnich
2007-06-25 17:53 ` Lyndon Nerenberg
2007-06-25 1:02 ` Dave Eckhardt
2007-06-24 12:14 ` erik quanstrom
2007-06-24 13:36 ` Lyndon Nerenberg
2007-06-24 21:47 ` erik quanstrom
2007-06-25 17:48 ` Lyndon Nerenberg
2007-06-25 18:46 ` erik quanstrom
2007-06-24 4:16 ` Bruce Ellis [this message]
2007-06-24 18:05 ` Skip Tavakkolian
2007-06-22 23:20 ` [9fans] About 9P Skip Tavakkolian
2007-06-22 23:48 ` Francisco J Ballesteros
2007-06-23 0:27 ` Roman Shaposhnick
2007-06-23 0:27 ` Francisco J Ballesteros
2007-06-23 12:08 ` erik quanstrom
2007-06-23 12:27 ` Francisco J Ballesteros
2007-06-23 12:57 ` Lucio De Re
2007-06-23 13:01 ` Uriel
2007-06-23 13:36 ` Francisco J Ballesteros
2007-06-23 14:27 ` Lucio De Re
2007-06-23 14:45 ` Francisco J Ballesteros
2007-06-22 21:16 ` Skip Tavakkolian
2007-06-22 21:37 ` Philippe Anel
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=775b8d190706232116u43d53d7bl71d0267a1b246be3@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@cse.psu.edu \
/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).