9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9bench: lmbench for Plan 9
Date: Sat, 22 Mar 2008 21:48:20 -0400	[thread overview]
Message-ID: <3dc25ba24213593ee0e4b2205af01a8a@quanstro.net> (raw)
In-Reply-To: <1d7d51759ce371d8fadc27c09b72548d@csplan9.rit.edu>

> As for the utility of the benchmarks, come on. I know there are people
> on this list who write kernel code (hmm, I seem to recall somebody
> on here who does a lot of work on networking drivers...) and they
> may find it useful to get these kinds of measurements to see if
> changes have improved performance. Besides, there's nothing to stop you
> from running the benchmarks on Linux and Plan 9 and comparing (for
> yourself) the difference in performance--you just can't try for
> e-cred by posting your results on comp.os.linux (hint: the
> comparisons don't come out very favorably for Plan 9 anyway).

i tend to use very simple timing runs in my testing.  i use dd for AoE
and disk drivers and a small program named zerohose for (other)
network protcols.  time(1) seems good enough for timing given an
appropriate amount of i/o.

the reason for the simple timing tests is because good hardware is
hard to get wrong but marginal hardware (bad design, undersized
buffers, unsufficient pcie lanes) is typically very sensitve to cache
pecularities.  even with simple tests some hardware can have >20%
variance between runs.  it's very hard to reason about this sort of
thing.  i'd hate to have to also have to understand what the benchmark
is doing for^wto me, too.

oh, plan 9 can push packets faster on the nics i've tested than linux,
but for some reason, plan 9 tcp performance hasn't been very good,
especially on 10gbe hardware.  il and aoe fair much better.

- erik



      reply	other threads:[~2008-03-23  1:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 17:21 john
2008-03-21 17:51 ` erik quanstrom
2008-03-21 18:55   ` ron minnich
2008-03-21 21:28     ` erik quanstrom
2008-03-22 11:18       ` hiro
2008-03-22 13:53         ` Francisco J Ballesteros
2008-03-22 13:56           ` erik quanstrom
2008-03-22 23:27             ` john
2008-03-23  1:48               ` erik quanstrom [this message]

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=3dc25ba24213593ee0e4b2205af01a8a@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).