From: "poczta.dotcom.pl" <myciel@dotcom.pl>
To: <nfs@lists.sourceforge.net>
Subject: Re: nfs performance problem
Date: Tue, 5 Nov 2002 20:55:41 +0100 [thread overview]
Message-ID: <007901c28505$51e9c240$640a010a@winda> (raw)
In-Reply-To: 20021105201758.I23227@vestdata.no
----- Original Message -----
From: "Ragnar Kj=F8rstad" <nfs@ragnark.vestdata.no>
To: "poczta.dotcom.pl" <myciel@dotcom.pl>
Cc: <nfs@lists.sourceforge.net>
Sent: Tuesday, November 05, 2002 8:17 PM
Subject: Re: [NFS] nfs performance problem
> On Tue, Nov 05, 2002 at 07:03:43PM +0100, poczta.dotcom.pl wrote:
> > Hi All
> >
> > I have really slow working nfs.
> > Server is build on:
> > - dual pentium Xeon 2GHz,
> > - 2 3ware 7500 controllers,
> > - raid 5 on 7 160GB discs on controler 1
> > - raid 5 on 6 160GB disks on cotroller 2
> >
> > Serwer is used for ~500k maildirs,
> > all clients (~20) are freebsd boxes, when nfs transfer is around 1MB/=
s
for writing and 1.5MB/s for reading
> > listing user directories even with very few file stakes up to 15
seconds.
> >
> > I tried nfs-ALL patch, but it didn' t help.
>
> How is local performance?
local read/writes are ok
> What filesystem do you use?
reiserfs on top of lvm (to be able to get snapshots)
> 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?
Linux 2.4.19 (hostname) 11/05/02
Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
dev8-0 16.16 205.52 82.84 3481842 1403528
dev8-1 160.58 1266.39 1346.12 21455002 22805744
Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
dev8-0 9.23 134.93 16.13 8096 968
dev8-1 150.92 753.20 1715.87 45192 102952
Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
dev8-0 10.02 135.07 26.53 8104 1592
dev8-1 152.78 763.33 1767.20 45800 106032
rafal
-------------------------------------------------------
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 20:01 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 [this message]
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
-- 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='007901c28505$51e9c240$640a010a@winda' \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox