From: Andreas Schuldei <andreas@schuldei.org>
To: Bernd Schubert <bernd-schubert@gmx.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs performance problem
Date: Thu, 25 Oct 2007 16:39:45 +0200 [thread overview]
Message-ID: <20071025141913.GD4499@jakobus.spotify.net> (raw)
* Bernd Schubert (bernd-schubert@gmx.de) [071025 15:54]:
> Hello Andreas,
>
> On Thursday 25 October 2007 15:10:29 Andreas Schuldei wrote:
> > lotta:/var/disks/sda on /var/disks/sda type nfs
> > (ro,hard,intr,proto=tcp,rsize=32k,addr=217.213.5.44) lotta:/var/disks/sdb
>
> try to increase rsize and wsize as much as possible, the maximum can be
> adjusted in /proc/fs/nfsd/max_block_size on the nfs server.
the with a max_block_size and rsize=512k i did not achive a noticable performance impact.
increasing it to 2M decreased the performance to 12-12Mbytes/s per disk. do i need to adjust more
tuneables to benefit from the increased size?
> > i was suspecting that the nfs server reads the files in too small
> > chunks and tried to help it with
> >
> > for i in a h i ; do ( echo $((1024*6)) >
> > /sys/block/sd$i/queue/read_ahead_kb ) ; done
>
> Are your partitions on lvm or md? This wouldn't help then, AFAIK for lvm you
> can't do it via /sys, but must always use blockdev
they are on xfs directly on disk, no lvm or md involved.
> > to get it to read in the files in one go.
> >
> > I would hope to at least double the speed. do
> > you have a benchmark tool that can tell me the latency? i tried
> > iozone and tried forcing it to only do read tests and did not get
> > any helpfull error or output at all.
>
> First of all, what is you *local* performance?
i mentioned that i get 50Mbyte/s out of each disk, even
when doing the dd on all four disks at the same time.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-10-25 14:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 14:39 Andreas Schuldei [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-25 13:10 nfs performance problem Andreas Schuldei
2007-10-25 13:53 ` Bernd Schubert
2007-10-27 9:25 ` Andreas Schuldei
2007-10-25 15:25 ` Chuck Lever
2007-10-25 19:34 ` Andreas Schuldei
2007-10-26 14:18 ` Chuck Lever
2007-10-26 17:01 ` Talpey, Thomas
2007-10-27 1:35 ` dean hildebrand
[not found] ` <c5befdd30710261835q50d34026h4dad32090db8a084@mail.gmail.co m>
2007-10-29 12:59 ` Talpey, Thomas
2002-11-07 15:19 Baker, Byran
2002-11-07 15:49 ` Matt Heaton
2002-11-07 17:32 ` Ragnar Kjørstad
2002-11-06 17:08 pwitting
2002-11-05 22:09 Lever, Charles
2002-11-05 20:56 Lever, Charles
2002-11-05 18:03 poczta.dotcom.pl
2002-11-05 19:17 ` Ragnar Kjørstad
2002-11-05 19:55 ` poczta.dotcom.pl
2002-11-05 20:22 ` Matt Heaton
2002-11-05 20:39 ` Benjamin LaHaise
2002-11-05 20:46 ` Matt Heaton
2002-11-05 21:24 ` Benjamin LaHaise
2002-11-05 23:32 ` Ragnar Kjørstad
2002-11-06 8:59 ` myciel
2002-11-06 10:16 ` Ragnar Kjørstad
2002-11-06 11:46 ` myciel
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=20071025141913.GD4499@jakobus.spotify.net \
--to=andreas@schuldei.org \
--cc=bernd-schubert@gmx.de \
--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