From: Eric Whiting <ewhiting@amis.com>
To: Jake Hammer <hammer@clarkisland.com>
Cc: NFS <nfs@lists.sourceforge.net>
Subject: Re: NFS read ok, write ok, simultaneous R+W=TERRIBLE
Date: Wed, 04 Dec 2002 22:01:04 -0700 [thread overview]
Message-ID: <3DEEDD90.915BAFF7@amis.com> (raw)
In-Reply-To: CFEAJJEGMGECBCJFLGDBMEHJCJAA.hammer@clarkisland.com
Jake,
Your results are similar to what I see -- I don't really have a
solution, but here are some things to consider:
1. Make sure your network is clean and doing duplex right. (test using
two ftp sessions moving those 10 gig files -- one reading while one
writes) Ftp will let you know if the TCP part of your network is healthy
under full duplex loads.
2. Try TCP mounts
3. Try NFS V3
4. Make sure your IDE RAID system on the server is healthy. Can it
handle concurrent read/write processes on the local box -- with NFS out
of the picture?
What is the filesystem you have on the RAID5 setup?
reiserfs/ext3/xfs/jfs?
What sort of IDE HW raid supports 14 disks? Or are you using SW raid?
I would like to see a solution to this sort of problem as well.
eric
Jake Hammer wrote:
>
> Hi All,
>
> I'm working with a 2.4.19 + all Neil Brown 2.4.19 patches on a P4 Xeon
> system, 2048MB ram, uniprocessor kernel. Distro is Debian Woody Stable. Disk
> subsystem is ATA RAID 5, 14 spindles. On writes from 15 100base-T clients
> via a Foundry switch, I am able to see 45MB/sec writes and 60MB/sec reads.
> Clients are DD'ing 10GB files to and from the box simultaneously. Mount =
> mount -o proto=udp,vers=2,wsize=32768,rsize=32768 bigbox:/space
>
> The problem is on read + write. As soon as the clients switch from read only
> or write only and do BOTH read and write, the CPU pegs and performance drops
> to 3MB/sec (three MB/s)! TOP shows that 4 of the NFSd's are consuming all of
> the CPU. It's like they are contending for some kind of resource like a lock
> or something.
>
> Any help would be sincerely appreciated. This is very strange behavior. It
> also happens with 2.4.18 + all Neil Brown patches for 2.4.18.
>
> Thanks,
>
> Jake Hammer
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Microsoft Visual Studio.NET
> comprehensive development tool, built to increase your
> productivity. Try a free online hosted session at:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET
comprehensive development tool, built to increase your
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-12-05 5:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 2:44 NFS read ok, write ok, simultaneous R+W=TERRIBLE Jake Hammer
2002-12-05 5:01 ` Eric Whiting [this message]
2002-12-05 5:55 ` Jake Hammer
2002-12-06 17:58 ` Paul Haas
2002-12-05 17:28 ` canon
2002-12-05 18:25 ` Eff Norwood
2002-12-05 18:35 ` Jake Hammer
2002-12-05 19:55 ` David Rees
2002-12-06 0:04 ` canon
[not found] <3DEEEC53.D24A1933@amis.com>
2002-12-05 6:27 ` Jake Hammer
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 10:32 trmcneal
[not found] <20021205192917.GA16871@hpti.com>
2002-12-05 19:47 ` Jake Hammer
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=3DEEDD90.915BAFF7@amis.com \
--to=ewhiting@amis.com \
--cc=hammer@clarkisland.com \
--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.