From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 18:25:27 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5169E813; Mon, 28 Oct 2013 18:25:27 +0000 (UTC) (envelope-from aurfalien@gmail.com) Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 242212353; Mon, 28 Oct 2013 18:25:27 +0000 (UTC) Received: by mail-pb0-f50.google.com with SMTP id uo5so4779806pbc.37 for ; Mon, 28 Oct 2013 11:25:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/P2Ss+Z1ml4fOoiue5EKRevYEqLdRZ+6YdZQOXIvelI=; b=VDl+P+9vfxcfk/2S9OChqIElWNtrZM37VgHP5A/g4HKbmtkl9adaNr90382G/pqJ6w suuSky+V1AvLYqtyn4vlEDI5i6tyCoWPq7HnAd3MZw6I6J+NY7NmUK7VqISC43pWiOSL jE1SSItGphRXXV8Lw01Nucn0tSD1NVTWCovuaK8wvKcQJOHAJG8SIyskjF5YO+fGEIRb OdMnJ6bfFGT1o7rWg54/suxvPOnmI9LE4Kh+DtuU5Y3ueYWq/HquYRDWlg3NPUA9Gzm9 RsyNqEE/ZGT01e2Q2U0nvVigaw+cuHQUIhrEreYRsU9YKLi2w5f821qv8uM9uLLIK06r 8/wA== X-Received: by 10.68.235.72 with SMTP id uk8mr17585581pbc.93.1382984726746; Mon, 28 Oct 2013 11:25:26 -0700 (PDT) Received: from briankrusicw.logan.tv ([64.17.255.138]) by mx.google.com with ESMTPSA id lm2sm36883671pab.2.2013.10.28.11.25.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Oct 2013 11:25:26 -0700 (PDT) Subject: Re: ZFS txg implementation flaw Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: aurfalien In-Reply-To: <20131028181631.GV63359@zxy.spb.ru> Date: Mon, 28 Oct 2013 11:25:25 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20131028092844.GA24997@zxy.spb.ru> <0F1D571E-2806-4392-A5EC-BE66A3C92BF7@gmail.com> <20131028181631.GV63359@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1085) Cc: freebsd-fs , freebsd-current@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 18:25:27 -0000 On Oct 28, 2013, at 11:16 AM, Slawa Olhovchenkov wrote: > On Mon, Oct 28, 2013 at 10:45:02AM -0700, aurfalien wrote: >=20 >>=20 >> On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov wrote: >>=20 >>> I can be wrong. >>> As I see ZFS cretate seperate thread for earch txg writing. >>> Also for writing to L2ARC. >>> As result -- up to several thousands threads created and destoyed = per >>> second. And hundreds thousands page allocations, zeroing, maping >>> unmaping and freeing per seconds. Very high overhead. >>>=20 >>> In systat -vmstat I see totfr up to 600000, prcfr up to 200000. >>>=20 >>> Estimated overhead -- 30% of system time. >>>=20 >>> Can anybody implement thread and page pool for txg? >>=20 >> Would lowering vfs.zfs.txg.timeout be a way to tame or mitigate this? >=20 > vfs.zfs.txg.timeout: 5 >=20 > Only x5 lowering (less in real case with burst writing). And more = fragmentation on writing and etc. So leave it default in other words. Good to know. - aurf