Date: Fri, 03 Jun 2011 16:57:18 -0300 From: Chris Forgeron <cforgeron@acsi.ca> To: Rick Macklem <rmacklem@uoguelph.ca>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: RE: Heads Up: default NFS server changing to the new one Message-ID: <BEBC15BA440AB24484C067A3A9D38D7E0164F4FB561E@server7.acsi.ca> In-Reply-To: <2075443640.480241.1303603218847.JavaMail.root@erie.cs.uoguelph.ca> References: <2075443640.480241.1303603218847.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
BTW, I've been pounding on the new NFS server with a few test VM's from my ESX cluster for the last 2 weeks, 24/7. Everything looks solid, no panics, no errors, no corruption. Memory usage is staying stable, so I haven't found any leaks. I'm using IOMETER to move a few TB of randomized data a day over the NFS link from each VM. However, ESX is only a NFS3 client, so my tests are not exercising any NFS4 based protocols. I hope to do a speed test comparison between new and old NFS servers this weekend - At this stage, my feeling is that the new NFS server is at least as fast. I suspect tests will show it to be faster (at least the code looks faster. :-) ). I'm going to expand testing by upgrading one of our non-critical SAN's to the latest code as well, so we'll see what it's like having 20 different workstations connecting daily and moving small files has on it. Good work on the new code.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BEBC15BA440AB24484C067A3A9D38D7E0164F4FB561E>