From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: Dirk Mueller <dmuell@gmx.net>, reiserfs-list@namesys.com
Subject: Re: Large Partition Performance Test
Date: 12 Apr 2002 09:21:22 -0400 [thread overview]
Message-ID: <1018617682.14429.119.camel@tiny> (raw)
In-Reply-To: <20020412134116.B21820@namesys.com>
On Fri, 2002-04-12 at 05:41, Oleg Drokin wrote:
> Hello!
>
> On Thu, Apr 11, 2002 at 06:11:23PM -0400, Chris Mason wrote:
>
> > Then I would expect the new allocator in busy_skip mode to fix it. But,
> > having profiling on would tell us for sure.
>
> Even withoyt skip_busy mode it will work much better.
> The problem is on each file creation we start to look for a free block almost
> from the beginning of disk. using no_unhashed_relocation mount option,
> we make initial block allocation to be more random and cause less overhead
> (verified).
> And in this test we create a lot of 15k files.
Ok, I'll buy that. The only way to know for sure is to give it a try or
profile the run, but I think it is very likely to be allocator related.
-chris
next prev parent reply other threads:[~2002-04-12 13:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 18:14 Large Partition Performance Test Bill Rees
2002-04-11 19:26 ` Hans Reiser
2002-04-11 19:43 ` Oleg Drokin
2002-04-11 20:28 ` Dirk Mueller
2002-04-11 22:11 ` Chris Mason
2002-04-12 9:41 ` Oleg Drokin
2002-04-12 13:21 ` Chris Mason [this message]
2002-04-12 13:32 ` Oleg Drokin
2002-04-11 19:48 ` Bill Rees
2002-04-12 9:39 ` Oleg Drokin
2002-04-12 13:21 ` Bill Rees
2002-04-12 13:29 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 19:28 Ivan Ivanov
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=1018617682.14429.119.camel@tiny \
--to=mason@suse.com \
--cc=dmuell@gmx.net \
--cc=green@namesys.com \
--cc=reiserfs-list@namesys.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.