From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966759Ab0B0Aqq (ORCPT ); Fri, 26 Feb 2010 19:46:46 -0500 Received: from mail-bw0-f209.google.com ([209.85.218.209]:62872 "EHLO mail-bw0-f209.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966740Ab0B0Aqo (ORCPT ); Fri, 26 Feb 2010 19:46:44 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=v0LzeXQOPLF3kS03nHiLYlTQR9+XNacxF9KxQ3hK8UQQLpM8KvrD9XwaXrH3NAY2KE l+GIQvE9yxxumO3/ntAhLbwrSA/Ujer8oBSSwqrMVplqt3eG18HyFwu30ei/AvNusPmq Mu1KPh1qVZvxGxmg/NgoP4Dgi8WAmWe1nYr98= From: Dmitry Monakhov To: Justin Piszcz Cc: "linux-ext4\@vger.kernel.org" , "linux-kernel\@vger.kernel.org" , Alan Piszcz Subject: Re: EXT4 is ~2X as slow as XFS (593MB/s vs 304MB/s) for writes? References: Date: Sat, 27 Feb 2010 03:46:39 +0300 In-Reply-To: (Justin Piszcz's message of "Sat, 27 Feb 2010 03:31:02 +0300") Message-ID: <87zl2vsdxs.fsf@openvz.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Justin Piszcz writes: > Hello, > > Is it possible to 'optimize' ext4 so it is as fast as XFS for writes? > I see about half the performance as XFS for sequential writes. > > I have checked the doc and tried several options, a few of which are shown > below (I have also tried the commit/journal_async/etc options but none of > them get the write speeds anywhere near XFS)? > > Sure 'dd' is not a real benchmark, etc, etc, but with 10Gbps between 2 > hosts I get 550MiB/s+ on reads from EXT4 but only 100-200MiB/s write. > > When it was XFS I used to get 400-600MiB/s for writes for the same RAID > volume. > > How do I 'speed' up ext4? Is it possible? I don't know how to speedup, but i do know how to slowdown XFS :) Seems that you forget to call fsync at the end of file write In this case some data may reside in memory cache. Please add "conv=fsync" or "conv=fdatasync" to the dd cmd. And redone your measurements. > > raid0_11 disks: (XFS) > # /dev/md0 /r1 xfs noatime 0 1 > p63:/r1# dd if=/dev/zero of=bigfile1 bs=1M count=10240 > 10240+0 records in > 10240+0 records out > 10737418240 bytes (11 GB) copied, 18.1021 s, 593 MB/s > p63:/r1# > > raid0_11 disks: (EXT4) > # /dev/md0 /r1 ext4 noatime 0 1 > # dd if=/dev/zero of=file bs=1M count=10240 > 10240+0 records in > 10240+0 records out > 10737418240 bytes (11 GB) copied, 35.3741 s, 304 MB/s > p63:/r1# > > Other tests (ext4) > p63:~# mount /dev/md0 /r1 -o data=writeback > p63:~# cd /r1 > p63:/r1# dd if=/dev/zero of=file bs=1M count=10240 > 10240+0 records in > 10240+0 records out > 10737418240 bytes (11 GB) copied, 39.8746 s, 269 MB/s > p63:/r1# > > p63:~# mount /dev/md0 /r1 -o data=writeback,nobarrier > p63:/r1# dd if=/dev/zero of=file bs=1M count=10240 > 10240+0 records in > 10240+0 records out > 10737418240 bytes (11 GB) copied, 40.0656 s, 268 MB/s > > Justin. > -- > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html