All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Dirk Mueller <dmuell@gmx.net>, reiserfs-list@namesys.com
Subject: Re: Large Partition Performance Test
Date: Fri, 12 Apr 2002 17:32:49 +0400	[thread overview]
Message-ID: <20020412173249.B23772@namesys.com> (raw)
In-Reply-To: <1018617682.14429.119.camel@tiny>

Hello!

On Fri, Apr 12, 2002 at 09:21:22AM -0400, Chris Mason wrote:
> > 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

OF course you'll buy that, because my suggested workaround worked ;)

> profile the run, but I think it is very likely to be allocator related.

First I decided I need a profile run, but once I realised how small created
files are, and looked on the on-disk block distribution chart.
Then I remembered on what basis we choose 1st block of a file to be allocated,
and I realised I do not need profile run ;)

In fact I am interested in similar task performance of ext3, since I've yet
to try it.

Bye,
    Oleg

  reply	other threads:[~2002-04-12 13:32 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
2002-04-12 13:32           ` Oleg Drokin [this message]
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=20020412173249.B23772@namesys.com \
    --to=green@namesys.com \
    --cc=dmuell@gmx.net \
    --cc=mason@suse.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.