Date: Wed, 31 Jul 2013 00:37:49 -0400 From: Joshua Boyd <boydjd@jbip.net> To: Berend de Boer <berend@pobox.com> Cc: freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: Terrible NFS4 performance: FreeBSD 9.1 + UFS/ZFS + AWS EC2 Message-ID: <CAHcKe7kapBR-YVPQHcWONzFpe-qQu%2BvDc_Z=6p%2BRPWesLOHF3A@mail.gmail.com> In-Reply-To: <874nbb7cys.wl%berend@pobox.com> References: <8761wfvwml.wl%berend@pobox.com> <153512858.1034456.1373755540674.JavaMail.root@uoguelph.ca> <874nbb7cys.wl%berend@pobox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Are you using EBS or ephemeral storage? If you are using EBS, how many provisioned IOPS and how many volumes are you using? In what configuration? What ec2 instance size are you using? Are you running your tests against the NFS server from within EC2, or from a host outside of EC2? On Tue, Jul 30, 2013 at 9:08 PM, Berend de Boer <berend@pobox.com> wrote: > >>>>> "Rick" == Rick Macklem <rmacklem@uoguelph.ca> writes: > > Rick> I think you mentioned that you were using a Linux client, > Rick> but not what version. I'd suggest a recent kernel from > Rick> kernel.org. (Fedora tracks updates/fixes for NFSv4 pretty > Rick> closely, so the newest Fedora release should be pretty > Rick> current.) > > This was Ubuntu 10.04 LTS. > > Have just tried a FreeBSD 9.1 client. Similar numbers. NFSv3 is about > 30% slower on FreeBSD than Linux: 3m30s versus 2m10s. NFSv4 has the > same terribly slow performance, i.e. 21m56s for the same test. > > Interestingly, the nfsd cpu usage doesn't rise as high as with > Linux. But goes up to 20% (instead of over 50%). > > I had a look at collectd measurements as well, one cpu on the FreeBSD > server is spending a lot of time in IRQ (whatever that means). > > BTS, this was a FreeBSD NFS4 out-of-the-box server, not with the patch > (as the patch didn't do that much for me, it did some, but performance > was still 8 times slower than nfs3). > > > Rick> All I can suggest is capturing packets and then emailing be > Rick> the captured packet trace. You can use tcpdump to do the > Rick> capture, since wireshark will understand it: # tcpdump -s 0 > Rick> -w <file>.pcap host <client-host> and then emailing me > Rick> <file>.pcap. > > Rick> I can take a look at the packet capture and maybe see what > Rick> is going on. > > Will email them shortly. > > -- > All the best, > > Berend de Boer > > > ------------------------------------------------------ > Awesome Drupal hosting: https://www.xplainhosting.com/ > -- Joshua Boyd E-mail: boydjd@jbip.net http://www.jbip.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHcKe7kapBR-YVPQHcWONzFpe-qQu%2BvDc_Z=6p%2BRPWesLOHF3A>