Date: Thu, 5 Apr 2018 20:15:45 +0500 From: "Eugene M. Zheganin" <eugene@zhegan.in> To: freebsd-stable@freebsd.org Subject: Re: TRIM, iSCSI and %busy waves Message-ID: <a11b8b16-e8ad-fd90-efb0-e1ccd49e11b2@zhegan.in> In-Reply-To: <2daf0677-3feb-6c4c-38d3-ed552f1a3cf0@multiplay.co.uk> References: <92b92a3d-3262-c006-ed5a-dc2f9f4a5cb9@zhegan.in> <2daf0677-3feb-6c4c-38d3-ed552f1a3cf0@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On 05.04.2018 19:57, Steven Hartland wrote: > You can indeed tune things here are the relevant sysctls: > sysctl -a | grep trim |grep -v kstat > vfs.zfs.trim.max_interval: 1 > vfs.zfs.trim.timeout: 30 > vfs.zfs.trim.txg_delay: 32 > vfs.zfs.trim.enabled: 1 > vfs.zfs.vdev.trim_max_pending: 10000 > vfs.zfs.vdev.trim_max_active: 64 > vfs.zfs.vdev.trim_min_active: 1 > vfs.zfs.vdev.trim_on_init: 1 > Well, I've already seen these. How do I tune them ? The idea of just tampering with them and seeing what will happen doesn't look like a bright one to me. Do I increase or decrease them ? Which ones do I have to avoid ? Eugene.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a11b8b16-e8ad-fd90-efb0-e1ccd49e11b2>