From owner-freebsd-fs@FreeBSD.ORG Mon Mar 30 15:57:42 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C20E24F4 for ; Mon, 30 Mar 2015 15:57:42 +0000 (UTC) Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 90C9275A for ; Mon, 30 Mar 2015 15:57:42 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 5799F168B for ; Mon, 30 Mar 2015 11:57:38 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Mon, 30 Mar 2015 11:57:41 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=gz3gREHf6CEmY3q cdc8XCePuHu8=; b=ieKOv+93EHwzIbv/DzY3J8MZtGEDIMM6cCP+zSS0kdSkGhx +ZNFhqfkiShy3y7oRVvx/zVLQVSIbA3GsMBTVRoQA42afnC/Bu2rcKT6SlG+0DVq kB4wqpUKVXrtzRCC25lgefGFmCw2+IMrPGVgqJz+XhRJPpxFnq3tOPf6qUdU= Received: by web3.nyi.internal (Postfix, from userid 99) id 1E9D510A621; Mon, 30 Mar 2015 11:57:41 -0400 (EDT) Message-Id: <1427731061.306961.247099633.0A421E90@webmail.messagingengine.com> X-Sasl-Enc: V8i8M7cbEVC/K9XMqjSLfpXKa8ZRr6C+6PDzjsDaEU7/ 1427731061 From: Mark Felder To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-0b3c2300 In-Reply-To: <5519716F.6060007@artem.ru> References: <55170D9C.1070107@artem.ru> <1427727936.293597.247070269.5CE0D411@webmail.messagingengine.com> <55196FC7.8090107@artem.ru> <1427730597.303984.247097389.165D5AAB@webmail.messagingengine.com> <5519716F.6060007@artem.ru> Subject: Re: Little research how rm -rf and tar kill server Date: Mon, 30 Mar 2015 10:57:41 -0500 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 15:57:42 -0000 On Mon, Mar 30, 2015, at 10:53, Artem Kuchin wrote: > > This is normal state, not under rm -rf > Do you need it during rm -rf ? > No, but I wonder if changing the timer from LAPIC to HPET or possibly one of the other timers makes the system more responsive under that load. Would you mind testing that? You can switch the timer like this: sysctl kern.eventtimer.timer=HPET And then run some of your I/O tests The full list of available timers is under sysctl kern.eventtimer.choice -- you could try any of them, but the higher the number next to the name is the higher perceived "quality" of the timer by the system. Note this doesn't survive a reboot, but could be set in /etc/sysctl.conf or /boot/loader.conf