9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fs performance
Date: Mon, 10 Jan 2011 11:53:54 -0800	[thread overview]
Message-ID: <AANLkTi=Mhn_BCbpAEvsKdzR15+R3xHqXJAd=E5ecA2m9@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=Gi-Ev4JhnJWKyptxH2XQ0uee8Xp7QfbrupdZe@mail.gmail.com>

I was using a slightly weird configuration, partially because it's the
hardware I had available, and partly because I thought it might more
adequately represent a typical internet connection. On one side of the
Linux bridge was a 10 Mbit hub, on the other side, a 100 Mbit switch.

The average latency was 500 us RTT.

Results may vary greatly when you bump up to gbit, but since the
Internet isn't gbit (and I can't afford gbit) I used much slower
hardware.

The testing setup and the results are all in the document; I
generalized a bit in my earlier email, in that streaming 9P had a
*slight* edge over regular 9P at 500 us RTT, but it's very slight. I
think at that point the bottleneck was bandwidth rather than latency,
and 9P was still able to get RPCs over as quickly as streams.


John

On Mon, Jan 10, 2011 at 10:48 AM, hiro <23hiro@googlemail.com> wrote:
> What bandwidth? With a gbit I could notice a difference. But probably
> the fault of the linux v9fs modules I used (half usec RTT).
>
> On 1/10/11, Francisco J Ballesteros <nemo@lsub.org> wrote:
>>>
>>> Right, my results were that you get pretty much exactly the same
>>> performance when you're working over a LAN whether you choose streams
>>> or regular 9P. Streaming only really starts to help when you're up
>>> into the multiple-millisecond RTT range.
>>
>> This is weird. Didn't read the thesis yet, sorry, but, do you know the
>> reason?
>> I think that when I measured op I found that even on lans, using get instead
>> of multiple rpcs was measurable. Of course users would not notice unless
>> latency
>> gets higher or many rpcs add their times.
>> thanks
>>
>>
>
>



  parent reply	other threads:[~2011-01-10 19:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09 17:06 erik quanstrom
2011-01-09 17:29 ` ron minnich
2011-01-09 17:51   ` John Floren
2011-01-10 18:07     ` Francisco J Ballesteros
2011-01-10 18:48       ` hiro
2011-01-10 19:06         ` erik quanstrom
2011-01-10 19:53         ` John Floren [this message]
2011-01-11 11:33           ` hiro
2011-01-09 18:31   ` erik quanstrom
2011-01-09 19:54   ` Bakul Shah
2011-01-09 20:25     ` ron minnich
2011-01-09 20:47       ` erik quanstrom
2011-01-09 21:04         ` ron minnich
2011-01-09 21:17       ` Bakul Shah
2011-01-09 21:59         ` erik quanstrom
2011-01-09 22:58         ` Charles Forsyth
2011-01-09 22:55           ` ron minnich
2011-01-09 23:50             ` Charles Forsyth
2011-01-10  3:26           ` Bakul Shah
2011-01-09 21:14     ` erik quanstrom
2011-01-09 21:38       ` Bakul Shah
2011-01-09 21:56         ` ron minnich
2011-01-09 22:02           ` erik quanstrom
2011-01-10 14:45           ` David Leimbach
2011-01-10 15:06             ` Charles Forsyth
2011-01-09 22:00         ` erik quanstrom
2011-01-10  3:57 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='AANLkTi=Mhn_BCbpAEvsKdzR15+R3xHqXJAd=E5ecA2m9@mail.gmail.com' \
    --to=slawmaster@gmail.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).