From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 10 12:08:46 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 540F6294 for ; Wed, 10 Oct 2012 12:08:46 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 0A9C28FC14 for ; Wed, 10 Oct 2012 12:08:45 +0000 (UTC) Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 10 Oct 2012 08:08:44 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id CD252B4035; Wed, 10 Oct 2012 08:08:44 -0400 (EDT) Date: Wed, 10 Oct 2012 08:08:44 -0400 (EDT) From: Rick Macklem To: Garrett Wollman Message-ID: <461825404.1975816.1349870924809.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20596.52616.867711.175010@hergotha.csail.mit.edu> Subject: Re: NFS server bottlenecks MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: Nikolay Denev , freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2012 12:08:46 -0000 Garrett Wollman wrote: > < said: > > > And, although this experiment seems useful for testing patches that > > try > > and reduce DRC CPU overheads, most "real" NFS servers will be doing > > disk > > I/O. > > We don't always have control over what the user does. I think the > worst-case for my users involves a third-party program (that they're > not willing to modify) that does line-buffered writes in append mode. > This uses nearly all of the CPU on per-RPC overhead (each write is > three RPCs: GETATTR, WRITE, COMMIT). > Yes. My comment was simply meant to imply that his testing isn't a realistic load for most NFS servers. It was not meant to imply that reducing the CPU overhead/lock contention of the DRC is a useless exercise. rick > -GAWollman