From: Erik Walthinsen <omega@pdxcolo.net>
To: nfs@lists.sourceforge.net
Subject: 2.6.5 NFS ready for production?
Date: Mon, 26 Apr 2004 10:38:00 -0700 [thread overview]
Message-ID: <1083001079.964.6.camel@localhost> (raw)
I'm trying to decide whether or not to even contemplate putting 2.6.5 on
our NAS server (single 2.4GHz Xeon, 512MB, 4x 200GB SATA on 3ware) to
gain the various I/O scheduling improvements, but obviously whether it's
even remotely possible depends primarily on whether NFS is up to it.
I have stock 2.6.5 on a test machine, and am getting *well* under
1MB/sec with bonnie++ over NFS on Gigabit (ttcp gets 18MB/sec, no jumbo
frames), compared to 20+MB/sec local (single old ATA disk). Haven't
tried to pin down what precisely is causing the issue, but it begs the
question: should I even be considering 2.6's NFS as production-capable
yet?
TIA,
- Omega
aka Erik Walthinsen
omega@pdxcolo.net
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-04-26 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 17:38 Erik Walthinsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-26 18:27 2.6.5 NFS ready for production? Lever, Charles
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=1083001079.964.6.camel@localhost \
--to=omega@pdxcolo.net \
--cc=nfs@lists.sourceforge.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