[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bad performance of 7.0 nfs client with Solaris nfs server
- To: "freebsd-performance_(_at_)_freebsd_(_dot_)_org" <freebsd-performance_(_at_)_freebsd_(_dot_)_org>
- Subject: Re: Bad performance of 7.0 nfs client with Solaris nfs server
- From: "Claus Guttesen" <kometen_(_at_)_gmail_(_dot_)_com>
- Date: Wed, 20 Feb 2008 13:09:48 +0100
- Cc: freebsd-questions <freebsd-questions_(_at_)_freebsd_(_dot_)_org>, Valerio Daelli <valerio_(_dot_)_daelli_(_at_)_gmail_(_dot_)_com>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=habmANXrZQZHpIey1WhFQMB8fNR6+OhJF8MEFgTyibM=; b=CLeiZm4pyexvTSIaNBIJRVcUa6wdQb2dpil0UFCI9S9bbYHfaR4ezXvo6V9hkhJnTKkGN95Je1UjuZ7H2iyFqSQFVOdUQ6HoTtcC+N+5CMAxAxUysuXLXan7V1aEXR0yEQFvruXKoDDSL5GrJsbDD5cSWdFNTSBGie4H0OQ1aVQ=
> > we have a FreeBSD 7.0 NFS client (csup today, built world and kernel).
> > It mounts a Solaris 10 NFS share.
> > We have bad performance with 7.0 (3MB/s).
> > We have tried both UDP and TCP mounts, both sync and async.
> > This is our mount:
> > nest.xx.xx:/data/export/hosts/bsd7.xx.xx/ /mnt/nest.xx.xx nfs
> > noatime,async,-i,rw,-T,-3
> > Both our server (7.0 and Solaris 10) are Gigabit Ethernet, both are HP
> > Proliant DL360 i386 (NIC bge0):
I have a solaris 9 nfs-server (on sparc) with som TB on HDS attached
to it with two qlogic-hba's. These partitions are shared to our
webservers via nfs, according to my mrtg-graph I get approx. 8 MB/s at
peak. I can probably get more but the requirement is not there.
With four-way-servers and FreeBSD 6.2 I had a read- and write-size of
8192. I ended up with this size by copying to and from the nfs-server
until I didn't get "nfs server not responding; is alive again"
message. Then I upgraded to FreeBSD 7.0 in October 2007 on a new
eight-way-server I started to get "not responding; alive again" during
load. So I decreased rw-size to the current 2048.
When I decreased the size I also avoided another problem (by accident
:-) ). When uploading images I sometimes saw ImageMagick's convert
went into an (almost) infinite loop, comsuming 100 % cpu (on one core)
until killed. Reducing the rw-size eliminated this issue.
my.nfs.server:/archive /archive nfs
rw,nfsv3,-w=2048,-r=2048 0 0
I'm using udp-mounts, does not appear to change performance for my part.
When lenity and cruelty play for a kingdom,
the gentlest gamester is the soonest winner.
freebsd-performance_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-performance-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org