Date: Tue, 9 Oct 2012 21:21:12 -0400 From: Garrett Wollman <wollman@bimajority.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: Nikolay Denev <ndenev@gmail.com>, freebsd-hackers@freebsd.org Subject: Re: NFS server bottlenecks Message-ID: <20596.52616.867711.175010@hergotha.csail.mit.edu> In-Reply-To: <1492364164.1964483.1349828280211.JavaMail.root@erie.cs.uoguelph.ca> References: <F865A337-7A68-4DC5-8B9E-627C9E6F3518@gmail.com> <1492364164.1964483.1349828280211.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Tue, 9 Oct 2012 20:18:00 -0400 (EDT), Rick Macklem <rmacklem@uoguelph.ca> 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). -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20596.52616.867711.175010>