Date: Thu, 21 Jan 2016 19:05:23 -0500 From: Mason Loring Bliss <mason@blisses.org> To: dweimer <dweimer@dweimer.net> Cc: freebsd-questions@freebsd.org Subject: Re: ZFS performance help sought Message-ID: <20160122000523.GL4538@blisses.org> In-Reply-To: <20160121235545.GK4538@blisses.org> References: <20160121205139.GG4538@blisses.org> <ea3f05f9a8c20bd62a1c391b432dafe2@dweimer.net> <20160121232810.GJ4538@blisses.org> <20160121235545.GK4538@blisses.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 21, 2016 at 06:55:45PM -0500, Mason Loring Bliss wrote: > Here's what I set: > > vfs.zfs.arc_max="4096M" > vfs.zfs.arc_min="1024M" > vfs.zfs.txg.timeout="3" > vfs.zfs.write_limit_override="512M" > > I'm not seeing any obvious way to verify the write_limit_override setting - > it appears not to show up in sysctl output. > > I'll wait for the current big transfer to finish and then I'll try it with > prefetch disabled too. Disabling prefetch doesn't do a thing here - the system is still painfully overloaded, doing something that was simply unproblematic under Linux. I'd be grateful for further debugging or tuning tips. Is it possible this has nothing to do with ZFS and that I need to play with FreeBSD's scheduling somehow? Again, FreeBSD 10.2, ZFS tuned at noted above, and with prefetch disabled. Eight gigs of RAM, pools less than 1TB. Doing a send/receive between pools on different disks is bringing the system to its knees, where the literal same hardware under Linux/ZoL doesn't break a sweat. What else can I try? -- Mason Loring Bliss (( "In the drowsy dark cave of the mind dreams mason@blisses.org )) build their nest with fragments dropped http://blisses.org/ (( from day's caravan." - Rabindranath Tagore
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160122000523.GL4538>