From owner-freebsd-current Sat Jul 15 07:25:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA27255 for current-outgoing; Sat, 15 Jul 1995 07:25:53 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA27248 for ; Sat, 15 Jul 1995 07:25:51 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id HAA12886; Sat, 15 Jul 1995 07:25:17 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id HAA00546; Sat, 15 Jul 1995 07:26:23 -0700 Message-Id: <199507151426.HAA00546@corbin.Root.COM> To: Bruce Evans cc: current@freebsd.org Subject: Re: slow nfsv3 writes In-reply-to: Your message of "Sun, 16 Jul 95 00:13:36 +1000." <199507151413.AAA23348@godzilla.zeta.org.au> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 15 Jul 1995 07:26:23 -0700 Sender: current-owner@freebsd.org Precedence: bulk >The speed of writes seems to be slower for nfsv3 according to iozone: > > iozone 1 512: 9055 bytes/sec > iozone 1 8192: 113028 bytes/sec > >Read speeds are good (800K and 1000K/sec) although this may be due to >local caching (it would take too long to test a large file size at >9055 bytes/sec :-). > >I don't know exactly what the write speeds used to be. I remember >something over 100K/sec and hoped for more. I don't remember such a >low speed for the small block size, except for a Linux client using >an unsuitable nfs block size. This is a known problem and started happening with some pre-2.0.5R changes. John has a work-around, but the problem needs to be better understood which is why I haven't done anything with his fix. -DG