From owner-freebsd-questions@FreeBSD.ORG Wed Dec 13 22:28:39 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2257816A415 for ; Wed, 13 Dec 2006 22:28:39 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-71-245-104-192.ptldor.fios.verizon.net [71.245.104.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DAD343CA1 for ; Wed, 13 Dec 2006 22:26:59 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.13.8/8.13.6) with ESMTP id kBDMSTL0023374 for ; Wed, 13 Dec 2006 14:28:29 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.13.8/8.13.4/Submit) with UUCP id kBDMSTEO023367 for freebsd-questions@freebsd.org; Wed, 13 Dec 2006 14:28:29 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id WAA11949; Wed, 13 Dec 2006 22:15:53 GMT Message-Id: <200612132215.WAA11949@sopwith.solgatos.com> To: freebsd-questions@freebsd.org Date: Wed, 13 Dec 2006 14:15:53 +0000 From: Dieter Subject: disk I/O tuning parameters X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Dec 2006 22:28:39 -0000 I've been experimenting with vfs.hirunningspace and it has some interesting effects. Is there a different, more detailed, description of its effects (and/or similar tuning parameters) than found in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-disk.html Is there a way to limit the runningspace, bufspace, or similar parameters on a per disk, per process, or per file basis rather than system wide? I haven't been able to find anything. I need a way to protect the disk I/O bandwidth of one process from other processes. Having its own disk, and running at rtprio is not sufficient. (See "processes not getting fair share of available disk I/O" thread in -questions for more details.)