From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger.kernel@dilger.ca>
Cc: Andrew Morton <akpm@linux-foundation.org>,
ext4 development <linux-ext4@vger.kernel.org>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 1/2] ext2: speed up file creates by optimizing rec_len functions
Date: Wed, 08 Dec 2010 15:07:32 -0600 [thread overview]
Message-ID: <4CFFF394.1020303@redhat.com> (raw)
In-Reply-To: <63DB7A38-7D0F-406E-8ACD-9CE5DB977DD9@dilger.ca>
On 12/08/2010 01:01 PM, Andreas Dilger wrote:
> On 2010-12-07, at 14:33, Andrew Morton wrote:
>> On Tue, 07 Dec 2010 15:22:55 -0600 Eric Sandeen
>> <sandeen@redhat.com> wrote:
>>> Retesting at a bunch of different number-of-files in bonnie (with
>>> a small sample size so probably a little noise)
>>>
>>> |files per sec| files stock patched delta 10,000 12300 14700
>>> +19% 20,000 6300 7600 +20% 30,000 4200 5000 +20% 40,000 3150
>>> 3700 +17% 50,000 2500 3000 +20%
>>>
>>> (again all on a 512MB ramdisk)
>>>
>>> *shrug* I'll believe my lyin' eyes, I guess. :)
>>
>> I bet other tweaks in there would yield similar goodliness.
>
> I think an important factor here is that this is being tested on a
> ramdisk, and is likely CPU bound, so any CPU reduction will directly
> be measured as a performance improvement. Probably oprofile is in
> order to see where other major CPU users are.
Yep, I ran oprofile.
samples % app name symbol name
1140046 41.8702 ext2.ko ext2_find_entry
1052117 38.6408 ext2.ko ext2_add_link
98424 3.6148 vmlinux native_safe_halt
40461 1.4860 vmlinux wait_on_page_read
29084 1.0682 vmlinux find_get_page
pretty slammed on those 2 ext2 functions! I think it's pretty
overwhelmed by the linear search.
-Eric
> In the past, ext3_mark_inode_dirty() was a major offender, and I
> recall that we discussed on the ext4 concall a mechanism to only copy
> the inode once per transaction so that overhead could be removed.
>
> Cheers, Andreas
>
>
>
>
>
next prev parent reply other threads:[~2010-12-08 21:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 17:47 [PATCH 0/2] ext2, ext3: speed up file create workloads Eric Sandeen
2010-12-07 17:51 ` [PATCH 1/2] ext2: speed up file creates by optimizing rec_len functions Eric Sandeen
2010-12-07 21:07 ` Andrew Morton
2010-12-07 21:22 ` Eric Sandeen
2010-12-07 21:33 ` Andrew Morton
2010-12-07 21:36 ` Eric Sandeen
2010-12-08 19:01 ` Andreas Dilger
2010-12-08 21:07 ` Eric Sandeen [this message]
2010-12-08 21:44 ` Andreas Dilger
2010-12-09 1:06 ` Ric Wheeler
2010-12-10 17:55 ` Ted Ts'o
2010-12-10 18:05 ` Ric Wheeler
2010-12-10 23:40 ` Andreas Dilger
2010-12-11 0:24 ` Eric Sandeen
2010-12-09 2:13 ` Eric Sandeen
2010-12-07 17:55 ` [PATCH 2/2] ext3: " Eric Sandeen
2011-01-06 14:47 ` [PATCH 0/2] ext2, ext3: speed up file create workloads Jan Kara
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=4CFFF394.1020303@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).