From: "Ragnar Kjørstad" <nfs@ragnark.vestdata.no>
To: "poczta.dotcom.pl" <myciel@dotcom.pl>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs performance problem
Date: Wed, 6 Nov 2002 00:32:37 +0100 [thread overview]
Message-ID: <20021106003237.L23227@vestdata.no> (raw)
In-Reply-To: <007901c28505$51e9c240$640a010a@winda>; from myciel@dotcom.pl on Tue, Nov 05, 2002 at 08:55:41PM +0100
On Tue, Nov 05, 2002 at 08:55:41PM +0100, poczta.dotcom.pl wrote:
> > How is local performance?
>=20
> local read/writes are ok
>=20
> > What filesystem do you use?
>=20
> reiserfs on top of lvm (to be able to get snapshots)
What reiserfs-version? 3.5 or 3.6?=20
What on-disk format? 3.5 or 3.6?
There should be an entry in the kernel-log from when the filesystem is
mounted.=20
Reiserfs-3.5 has some known performance-problems related to NFS - that
may be your problem.
> > What's the output from "iostat -x -d -k 60 3"?
> >
> below is output from 'iostat -d 60 3' (- my iostat does not take '-k'
> option,
> and '-d' gives me empty output) - mayby this is enough?
And not -x either?
iostat fr=E5 sysstat-4.0.3-2 (from RedHat) includes a "-x" option for
extended output. Most importantly, it will tell how much of the time
each device is busy.
It's unclear from your posts if this is a io-related problem or not.
Unnless you're running reiserfs-3.5 my guess is that it is the
IO-performance that is the problem. 3ware 7500 controllers have rather=20
poor performance on RAID5 - especially for writes.=20
If that's correct, then switching to a different RAID-level or replacing
the 3ware-controller should solve the problem. SCSI- or FC- RAIDS are
easily 10 or 20 times faster than the 3ware RAID for some types of
operations, and if you want something cheaper there is also different
types of IDE-RAIDs.
--=20
Ragnar Kj=F8rstad
Big Storage
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-11-05 23:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 18:03 nfs performance problem 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 [this message]
2002-11-06 8:59 ` myciel
2002-11-06 10:16 ` Ragnar Kjørstad
2002-11-06 11:46 ` myciel
-- strict thread matches above, loose matches on Subject: below --
2002-11-05 20:56 Lever, Charles
2002-11-05 22:09 Lever, Charles
2002-11-06 17:08 pwitting
2002-11-07 15:19 Baker, Byran
2002-11-07 15:49 ` Matt Heaton
2002-11-07 17:32 ` Ragnar Kjørstad
2007-10-25 13:10 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
2007-10-25 14:39 Andreas Schuldei
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=20021106003237.L23227@vestdata.no \
--to=nfs@ragnark.vestdata.no \
--cc=myciel@dotcom.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.