From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] wrarenas
Date: Fri, 24 Apr 2009 13:56:01 -0400 [thread overview]
Message-ID: <f7cded55ecd8eaf3784ae8126c37edc7@coraid.com> (raw)
In-Reply-To: <755cee220967127b18c63c0f03fd1545@quintile.net>
and, writing should take the same amount of
time as reading. that is you can switch -if and -of
and you should get the same results.
it could be that you are seeking around all over
the place. on modern hardware, if you are doing
significant seeks between each write, you can get down
below 1mb/s.
i addressed this problem in the diskless fileserver paper.
- erik
next prev parent reply other threads:[~2009-04-24 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 17:49 Steve Simon
2009-04-24 17:54 ` erik quanstrom
2009-04-24 17:56 ` erik quanstrom [this message]
2009-04-28 22:45 ` Russ Cox
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=f7cded55ecd8eaf3784ae8126c37edc7@coraid.com \
--to=quanstro@coraid.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).