From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Bron Gondwana" Subject: Re: Phoronix article slaming BTRFS Date: Wed, 24 Jun 2009 05:31:34 -0400 Message-ID: <1245835894.6366.1321909165@webmail.messagingengine.com> References: <2d23818a0906231026g6e4567fdv8eda3d6c4828ef4d@mail.gmail.com> <2d23818a0906231028t43d97e64t901610ca18e749d0@mail.gmail.com> <7a329d910906231920l49236acer404369643a2cf833@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "Mike Ramsey" , linux-btrfs@vger.kernel.org Return-path: In-Reply-To: List-ID: On Tue, 23 Jun 2009 22:47 +0000, "Mike Ramsey" wrote: > Wil Reichert gmail.com> writes: > > My suggestion is either to show where their > > benchmarks are in err, > > I did this, didn't I? > 1. Vertex with write cache enabled; disabled would have seen a > 2X improvement. > 2. Error in libata Meaning that nobody can turn off the write cache in linux without deep kernel hackery. Sounds to me like they are benchmarking the real world rather than trying to favour btrfs by making changes that are unlikely to be viable for anyone trying to run it in production. I.e. they're benchmarking reality. Sure there are ways that btrfs performance could be improved, but they're not realistically available to mortals selecting "use btrfs for /home" in their Ubuntu "Bleeding-Edge Badger" release. Bron. -- Bron Gondwana brong@fastmail.fm