From owner-freebsd-bugs Tue Oct 8 11:34:37 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13625 for bugs-outgoing; Tue, 8 Oct 1996 11:34:37 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA13618 for ; Tue, 8 Oct 1996 11:34:34 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.6/8.7.3) id OAA01563 for freebsd-bugs@freebsd.org; Tue, 8 Oct 1996 14:34:31 -0400 (EDT) From: Charles Henrich Message-Id: <199610081834.OAA01563@crh.cl.msu.edu> Subject: NFS from Solaris Server To: freebsd-bugs@freebsd.org Date: Tue, 8 Oct 1996 14:34:30 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is Hosed, on 2.1.0 NFS will write to a sun server at a whopping 100K/sec over ethernet, but it goes along happily just slowly. On 2.2-961006-SNAP we also write to NFS at a whopping 100K/sec, however in 8MB increments we write out at 600K/sec (apparently into some memory buffer??) at which point the buffer fills, all NFS operations are locked out on the system until the buffer is drained. This takes an eternity. How do I undo this buffering mechanism or make it a tunable? Also an interesting note, a SGI to the SUN writes at 900K/sec via NFS with no problems. The SGI is apparently doing: NFS v3 Proc 6, Proc 7 (Data) The FreeBSD box does: NFS v2 Proc 8 (Data) or NFS v3 Proc 7 (Data) Both are horrendously slow. Im going to attempt to figure out what the hell Proc 6 is (everything I see says read, which doesnt make alot of sense). In any case Im not much of a kernel hacker, so any assistance or someone with a solution, please raise your hand! :) -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich