[OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance
Dan McDonald
danmcd at kebe.com
Thu Aug 24 13:35:35 UTC 2017
> On Aug 24, 2017, at 8:41 AM, Schweiss, Chip <chip at innovates.com> wrote:
>
> I just move one of my production systems to OmniOS CE 151022m from 151014 and my NFS performance has tanked.
>
> Here's a snapshot of nfssvrtop:
>
> 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite: 104 KB, awrite: 9634 KB
> Ver Client NFSOPS Reads SWrites AWrites Commits Rd_bw SWr_bw AWr_bw Rd_t SWr_t AWr_t Com_t Align%
> 3 10.28.17.1 0 0 0 0 0 0 0 0 0 0 0 0 0
> 3 all 0 0 0 0 0 0 0 0 0 0 0 0 0
> 4 10.28.17.1 9 0 0 0 0 0 0 0 0 0 0 0 0
> 4 10.28.16.160 17 0 0 0 0 0 0 0 0 0 0 0 0
> 4 10.28.16.127 20 0 0 0 0 0 0 0 0 0 0 0 0
> 4 10.28.16.113 74 6 6 0 0 48 56 0 1366 20824 0 0 100
> 4 10.28.16.64 338 16 0 36 3 476 0 1065 120 0 130 117390 100
> 4 10.28.16.54 696 68 0 91 5 2173 0 2916 52 0 93 142083 100
> 4 all 1185 90 6 127 8 2697 56 3996 151 20824 104 133979 100
>
> The pool is not doing anything but serving NFS. Before the upgrade, the pool would sustain 20k NFS ops.
>
> Is there some significant change in NFS that I need to adjust its tuning?
Oh my.
I'd start pinging the illumos list on this. Also, are there any special tweaks you made in the 014 configuration? IF you did, I'd start back removing them and seeing what a default system does, just in case.
I know Delphix and Nexenta still care about NFS quite a bit, so I can't believe something would be that bad.
Maintainers: Check for NFS changes RIGHT AFTER 022 closed for blanket upstream pull-ins. Maybe it closed during a poor-performance window?
Dan
More information about the OmniOS-discuss
mailing list