From owner-freebsd-stable Wed Nov 8 17:55:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 0C23637B4C5 for ; Wed, 8 Nov 2000 17:55:34 -0800 (PST) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 13tgw6-0001QV-00; Wed, 08 Nov 2000 17:55:30 -0800 Date: Wed, 8 Nov 2000 17:55:25 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Brian Behlendorf Cc: stable@freebsd.org Subject: Re: disk I/O In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Nov 2000, Brian Behlendorf wrote: > Ideas? This is actually during a more lightly loaded time period. It > just "feels" like I should be able to push more than 80-100 tps through > da0 (lots of small writes and fsyncs, admittedly) and more than 150tps on > da1 (which is almost all reads). Anything else I should be looking at? A 100tps average is about 10ms per transfer. A good hard drive takes about 8ms average per seek. Assuming every transfer requires a seek, you are not doing too badly. However, tagged commands allow multiple pending IOs per disk. If tags are disabled, or not functioning you will not get this benefit. See camcontrol. Also, mounting your disks with noatime (mount -u -o noatime /blah) requires no downtime and immediately improvement for a lot of things. Basically, it elimiates an IO to update the atime on files and directories. Also, softupdates will be very helpful, but will probably require a reboot. > Brian Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message