Date: Wed, 27 Oct 2004 22:22:35 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: ben@timing.com Cc: current@freebsd.org Subject: Re: -current NFSv2 and NFSv3 issues Message-ID: <20041027.222235.25072396.imp@bsdimp.com> In-Reply-To: <16767.52483.986921.670394@piglet.timing.com> References: <16767.52483.986921.670394@piglet.timing.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <16767.52483.986921.670394@piglet.timing.com>
Ben Mesander <ben@timing.com> writes:
: things complete succesfully, but buildworld -j1 of -current takes 5
: hours over dedicated 100baseT network, and the ethernet never gets
: even close to being saturated, so the underlying network transport
: doesn't seem to be the bottleneck.
By comparison, it takes 35 minutes on a local disk. And sometimes,
when there's only one user, it takes 45-55 minutes. The problem
appears to get worse exponentially with the number of concurrent nfs
requests.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041027.222235.25072396.imp>