From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 18 09:09:16 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4826486B; Fri, 18 Jan 2013 09:09:16 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [188.252.31.196]) by mx1.freebsd.org (Postfix) with ESMTP id ABEEB81E; Fri, 18 Jan 2013 09:09:15 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id r0I99CHv010388; Fri, 18 Jan 2013 10:09:12 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id r0I99BeB010385; Fri, 18 Jan 2013 10:09:11 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Fri, 18 Jan 2013 10:09:11 +0100 (CET) From: Wojciech Puchar To: Stefan Esser Subject: Re: stupid UFS behaviour on random writes In-Reply-To: <50F90C0F.5010604@freebsd.org> Message-ID: References: <103826787.2103620.1358463687244.JavaMail.root@erie.cs.uoguelph.ca> <50F90C0F.5010604@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Fri, 18 Jan 2013 10:09:12 +0100 (CET) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2013 09:09:16 -0000 > > But I doubt that such a change would improve performance in the you doubt but i am sure it would improve it a lot. Just imagine multiple VM images on filesystem, running windoze with 4kB cluster size, each writing something. no matter what is written from within VM it ends up as read followed by write, unless blocks are already in buffer cache.