From: Ric Wheeler <rwheeler@redhat.com>
To: rwheeler@redhat.com
Cc: "Theodore Tso" <tytso@mit.edu>,
"Frédéric Bohé" <frederic.bohe@bull.net>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/4] Create the journal in the middle of the filesystem
Date: Wed, 03 Sep 2008 10:08:04 -0400 [thread overview]
Message-ID: <48BE9A44.10103@redhat.com> (raw)
In-Reply-To: <48B6B86F.5060106@redhat.com>
Ric Wheeler wrote:
> Theodore Tso wrote:
>> On Thu, Aug 28, 2008 at 09:40:30AM -0400, Ric Wheeler wrote:
>>
>>> I can try and test this with my fsync() heavy fs_mark run...
>>>
>>>
>>
>> Given [1] I have no doubt that you should see a difference between
>> mke2fs from e2fsprogs 1.41.0 (which will allocate the journal at the
>> beginning of the filesystem) and the latest tip of e2fsprogs.
>>
>> It would be interesting to see how measurable the difference is,
>> though. I'd recommend doing "mke2fs -t ext4dev" using both versions
>> of mke2fs, and seeing how much the difference it makes.
>>
>> [1]
>> http://www.usenix.org/events/usenix05/tech/general/full_papers/prabhakaran/prabhakaran_html/main.html#fig-journal-location-withinfs-fix
>>
>>
>> - Ted
>>
>>
>
> I was thinking of trying this on a much larger disk (1TB) - the
> article reports on a 4GB partition which is pretty tiny,
>
> ric
Using Ted's new journal in the middle mkfs & hacking it slightly to make
the journal go back to block 0, I ran some quick tests to try and
measure an impact of the journal placement (multiple threads writing 4MB
files).
The results that are most clear are certainly that delayed allocation is
a big win, the journal placement has mostly a positive impact on the
write performance, but the results are quite close.
Starting with a newly created file system, each pass put down 16,000 4MB
files:
Count Files/sec - ZERO Files/sec - Middle
16000 20.8 20.8
32000 19.2 18.4
48000 16.0 14.4
64000 20.8 20.8
80000 20.8 20.8
96000 20.8 20.8
112000 20.8 20.8
128000 19.2 20.8
144000 19.2 19.2
160000 17.6 19.2
176000 16.6 17.6
192000 16.0 16.0
208000 14.4 14.4
224000 12.8 14.4
With no delayed allocation:
Count Files/sec - ZERO Files/sec - Middle
16000 16.0 16.0
32000 16.0 16.0
48000 16.0 16.0
64000 16.0 14.8
80000 14.4 14.4
96000 14.1 14.4
112000 12.8 12.8
128000 11.2 11.2
144000 11.2 12.8
160000 14.4 14.4
176000 11.3 12.8
192000 14.9 12.8
208000 16.0 16.0
224000 14.4 16.0
ric
next prev parent reply other threads:[~2008-09-03 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 17:36 Journal file fragmentation Frédéric Bohé
2008-08-27 20:12 ` Jose R. Santos
2008-08-27 21:06 ` Theodore Tso
2008-08-27 21:14 ` [PATCH 1/4] ext2fs_mkjournal(): Don't allocate an extra block to the journal Theodore Ts'o
2008-08-27 21:14 ` [PATCH 2/4] Create the journal in the middle of the filesystem Theodore Ts'o
2008-08-27 21:14 ` [PATCH 3/4] ext2fs_block_iterate2: Add BLOCK_FLAG_APPEND support for extent-based files Theodore Ts'o
2008-08-27 21:14 ` [PATCH 4/4] If the filesystem supports extents create an extent-based journal inode Theodore Ts'o
2008-08-28 9:55 ` [PATCH 2/4] Create the journal in the middle of the filesystem Frédéric Bohé
2008-08-28 13:34 ` Theodore Tso
2008-08-28 13:40 ` Ric Wheeler
2008-08-28 14:36 ` Theodore Tso
2008-08-28 14:38 ` Ric Wheeler
2008-09-03 14:08 ` Ric Wheeler [this message]
2008-08-28 16:16 ` Frédéric Bohé
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=48BE9A44.10103@redhat.com \
--to=rwheeler@redhat.com \
--cc=frederic.bohe@bull.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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