From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/3] ocfs2: Inode Allocation Strategy Improvement.v2
Date: Sun, 18 Jan 2009 07:17:24 -0800 [thread overview]
Message-ID: <73490225-F30E-4CF1-ACCE-FBCA845ACBDC@oracle.com> (raw)
In-Reply-To: <4972EF47.5090202@oracle.com>
How big is this disk? Maybe one kernel tree untar is not be enough to
expose the original issue. Also, use ls -i and/or debugfs to see if
the inodes have some locality.
On Jan 18, 2009, at 12:58 AM, Tao Ma <tao.ma@oracle.com> wrote:
>
>
> tristan.ye wrote:
>> On Fri, 2009-01-16 at 16:16 +0800, Tao Ma wrote:
>>
>>> tristan.ye wrote:
>>>
>> Tao,
>>
>> I've done 10 times tests with single-node testcase repeatly,
>> following
>> is a average statistic reports
>> =============== Tests with 10 times iteration================
>>
>> 1st 'Tar xjvf' result:
>>
>> Average real time with 10 times:
>> Original kernel kernel with enhanced
>> patches
>> 0m 43.578s 0m 49.355s
>>
>> 1st 'ls -lR' result:
>> Average real time with 10 times:
>> Original kernel kernel with enhanced
>> patches
>> 0m 23.622s 0m 23.508s
>>
>> 1st 'rm -rf' result:
>> Average real time with 10 times:
>> Original kernel kernel with enhanced
>> patches
>> 0m 57.039s 0m 58.612s
>>
>> 2rd 'Tar xjvf' result:
>> Average real time with 10 times:
>> Original kernel kernel with enhanced
>> patches
>> 0m 49.550s 0m 52.214s
>>
>> 2rd 'ls -lR' result:
>> Average real time with 10 times:
>> Original kernel kernel with enhanced
>> patches
>>
>> 0m 23.591s 0m 23.487s
>>
>> ===============Tests end============================
>>
>>
>>> From above tests, we really have had a speed-up performance gain
>>> when
>> traversing files by 'ls -lR' against a kernel tree:),but seems also
>> encountered a performance lose when populating the files by 'tar
>> xvjf'
>> according to the contrast tests.
>>
> I am just a little confused with your test result. Especially the
> last one.
> from the statistics, it looks that there is almost no performance gain
> comparing 0m23.591s with 0m 23.487s.
> But I see >2mins every time. So are you sure of it?
> anyway, thanks for your test and I will discuss it with you later.
>
> Regards,
> Tao
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2009-01-18 15:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 21:58 [Ocfs2-devel] [PATCH 0/3] ocfs2: Inode Allocation Strategy Improvement.v2 Tao Ma
2009-01-15 22:00 ` [Ocfs2-devel] [PATCH 1/3] ocfs2: Optimize inode allocation by remembering last group Tao Ma
2009-01-15 22:00 ` [Ocfs2-devel] [PATCH 2/3] ocfs2: Allocate inode groups from global_bitmap Tao Ma
2009-01-15 22:00 ` [Ocfs2-devel] [PATCH 3/3] ocfs2: Optimize inode group allocation by recording last used group Tao Ma
2009-01-16 8:05 ` [Ocfs2-devel] [PATCH 0/3] ocfs2: Inode Allocation Strategy Improvement.v2 tristan.ye
2009-01-16 8:16 ` Tao Ma
2009-01-16 16:08 ` tristan.ye
2009-01-18 8:58 ` Tao Ma
2009-01-18 15:17 ` Sunil Mushran [this message]
2009-01-19 7:07 ` tristan.ye
2009-01-19 7:15 ` Tao Ma
2009-01-19 12:57 ` tristan.ye
2009-01-19 18:35 ` Sunil Mushran
2009-01-20 2:34 ` tristan.ye
2009-01-21 2:37 ` Sunil Mushran
2009-01-18 15:18 ` Sunil Mushran
2009-02-13 2:42 ` tristan.ye
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=73490225-F30E-4CF1-ACCE-FBCA845ACBDC@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.