public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Jon Burgess <lkml@jburgess.uklinux.net>
Cc: Rik van Riel <riel@redhat.com>,
	linux kernel <linux-kernel@vger.kernel.org>,
	reiserfs-dev <reiserfs-dev@namesys.com>
Subject: Re: ext2/3 performance regression in 2.6 vs 2.4 for small interleaved writes
Date: Thu, 12 Feb 2004 12:17:04 -0800	[thread overview]
Message-ID: <402BDF40.5040601@namesys.com> (raw)
In-Reply-To: <402B580E.3000404@jburgess.uklinux.net>

Jon Burgess wrote:

> Rik van Riel wrote:
>
>> Just for fun, could you also try measuring how long it takes
>> to read back the files in question ?
>>
>> Both individually and in parallel...
>>
> The original code did the read back as well, I stripped it out to make 
> the code smaller to post.
> It was the read back performance that I was most interested in. I 
> found that ext2/3 interleave all the blocks on the disk. With 2 stream 
> the read performance is 50%, 4 streams give 25% etc.
>
> I have one really bad case where I record a TV stream at 500kByte/s + 
> a radio one at 25kByte/s. These blocks are interleaved on the disk and 
> the read performance of the radio stream is reduced by the data ratio, 
> i.e. 1:20, so I get a miserable read performance of ~ 1MB/s.
>
> I found that ext2, ext3 and Reiserfs behave similarly.

Try Reiser4, it will probably cure it for you nicely.  I will be 
surprised if it does not, please let me know your results.  I would 
expect that tweaking the block preallocation code to preallocate more 
should cure it for ReiserFS V3 also....

> XFS and JFS appear to coalesce the data blocks during the write phase 
> and can read the data back at near maximum performance.
>
>    Jon
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>


  reply	other threads:[~2004-02-12 20:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11 19:04 ext2/3 performance regression in 2.6 vs 2.4 for small interleaved writes Jon Burgess
2004-02-11 20:28 ` Rik van Riel
2004-02-11 21:02   ` Michael Frank
2004-02-11 21:18     ` Diego Calleja
2004-02-12  2:00       ` Dave Olien
2004-02-12  2:23         ` Andrea Arcangeli
2004-02-12  9:42           ` ext2/3 performance regression in 2.6 vs 2.4 for small interl Giuliano Pochini
2004-02-12 10:15             ` John Bradford
2004-02-12 10:27             ` Nick Piggin
2004-02-12 17:05               ` Michael Frank
2004-02-12 17:18                 ` Valdis.Kletnieks
2004-02-12 20:55                   ` Helge Hafting
2004-02-13  1:57                     ` Jamie Lokier
2004-02-13  2:05                       ` Nick Piggin
2004-02-12 14:59             ` Andrea Arcangeli
2004-02-13 12:15     ` ext2/3 performance regression in 2.6 vs 2.4 for small interleaved writes Jon Burgess
2004-02-12 10:40   ` Jon Burgess
2004-02-12 20:17     ` Hans Reiser [this message]
2004-02-12  9:56 ` Andrew Morton
2004-02-12 20:20   ` Jon Burgess
2004-02-13  8:28     ` Juan Piernas Canovas
2004-02-16 17:51     ` Alex Zarochentsev
2004-02-16 20:03       ` Jon Burgess
2004-02-13 12:35   ` Jon Burgess
2004-02-14 15:00   ` Jon Burgess

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=402BDF40.5040601@namesys.com \
    --to=reiser@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@jburgess.uklinux.net \
    --cc=reiserfs-dev@namesys.com \
    --cc=riel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox