From owner-freebsd-current@FreeBSD.ORG Sat Jul 13 17:29:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D6E6445D; Sat, 13 Jul 2013 17:29:41 +0000 (UTC) (envelope-from ianf@cloudseed.co.za) Received: from zcs03.jnb1.cloudseed.co.za (zcs03.jnb1.cloudseed.co.za [41.154.0.139]) by mx1.freebsd.org (Postfix) with ESMTP id 706831A2F; Sat, 13 Jul 2013 17:29:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zcs03.jnb1.cloudseed.co.za (Postfix) with ESMTP id DBA962B43283; Sat, 13 Jul 2013 19:29:39 +0200 (SAST) X-Virus-Scanned: amavisd-new at zcs03.jnb1.cloudseed.co.za Received: from zcs03.jnb1.cloudseed.co.za ([127.0.0.1]) by localhost (zcs03.jnb1.cloudseed.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FAnb8fEPSe0X; Sat, 13 Jul 2013 19:29:38 +0200 (SAST) Received: from clue.co.za (unknown [41.154.88.19]) by zcs03.jnb1.cloudseed.co.za (Postfix) with ESMTPSA id 6A9412B43262; Sat, 13 Jul 2013 19:29:38 +0200 (SAST) Received: from localhost ([127.0.0.1] helo=zen) by clue.co.za with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1Uy3dY-0003tu-En; Sat, 13 Jul 2013 19:29:36 +0200 To: Konstantin Belousov From: Ian FREISLICH Subject: Re: Filesystem wedges caused by r251446 In-Reply-To: <20130713164814.GM91021@kib.kiev.ua> References: <20130713164814.GM91021@kib.kiev.ua> <20130713054220.GJ91021@kib.kiev.ua> <20130712201051.GI91021@kib.kiev.ua> <201307110923.06548.jhb@freebsd.org> <201307091202.24493.jhb@freebsd.org> X-Attribution: BOFH Date: Sat, 13 Jul 2013 19:29:36 +0200 Message-Id: X-Mailman-Approved-At: Sat, 13 Jul 2013 17:33:04 +0000 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jul 2013 17:29:41 -0000 Konstantin Belousov wrote: > > So, then did r251446 actually start using this value or did other > > values get significantly tuned up? I recall now setting this nearly > > a year ago when we did our ZFS tuning and it was a four fold increase > > on the defaults. > > r251446 optimized the wakeups by only doing wakeups when runningbufspace > actually crossed the lorunningspace. Before, wakeups were performed > always on the runningbufspace changes. > > For ZFS, these settings are completely irrelevant, ZFS does not use > buffer cache. A year is so long ago... It might have been tuning for our postgres servers. It might be worth while putting in a sanity check that doesn't allow hirunningspace to be set lower than lorunningspace. Thanks for your patience. Ian -- Ian Freislich