From owner-freebsd-stable@freebsd.org Sat Apr 7 06:19:58 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36ECCF8C332 for ; Sat, 7 Apr 2018 06:19:58 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 97BD786329 for ; Sat, 7 Apr 2018 06:19:57 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from [192.168.243.11] ([192.168.243.11]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTP id w376JpoZ057256 for ; Sat, 7 Apr 2018 11:19:52 +0500 (YEKT) (envelope-from emz@norma.perm.ru) Subject: Re: TRIM, iSCSI and %busy waves To: freebsd-stable@freebsd.org References: <92b92a3d-3262-c006-ed5a-dc2f9f4a5cb9@zhegan.in> <2daf0677-3feb-6c4c-38d3-ed552f1a3cf0@multiplay.co.uk> From: "Eugene M. Zheganin" Message-ID: Date: Sat, 7 Apr 2018 11:19:06 +0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: ru X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2018 06:19:58 -0000 Hi, 05.04.2018 20:15, Eugene M. Zheganin 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 ? > So, about these - are there any best practices to fine-tune them ? How do you tune them (I won't blame anyone for examples) ?  Or are they "just there" and nobody touches them ? Thanks. Eugene.