All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: "David Masover" <ninja@slaphack.com>,
	"Pierre Etchemaïté" <petchema@concept-micro.com>,
	reiserfs-list@namesys.com
Subject: Re: [PATCH] reiserfs: on-demand bitmap loading (testing only)
Date: Sat, 09 Jul 2005 00:46:55 -0700	[thread overview]
Message-ID: <42CF80EF.7030204@namesys.com> (raw)
In-Reply-To: <42CEF308.5070302@suse.com>

Jeff Mahoney wrote:

>
>
> The results showed that delayed allocation was only slightly faster than
> waiting on the buffers. The reason for this is that the majority of the
> time is actually spent issuing the block read requests, not actually
> waiting for their results. 

Can you define "spent issuing"?  Perhaps this is simply a bad choice of
block device congestion configuration, and changing it would fix
things.  Because device congestion is based on NUMBER of requests, not
their size, bitmap reading would congest things more than file IO.

Block device congestion limits I suspect to be in need of serious
review, not just because of bitmaps.....

> The amount of time waiting on the blocks
> appears not to change radically, though the amount of time issuing the
> read requests does.
>
> Here are the actual numbers from the test runs. Between each mount
> attempt, I attempted to clear the system caches by allocating and
> writing to all the memory on the system, as well as the disk caches by
> reading 50 MB from disk. I performed the tests with four block sizes in
> order to increase the number of bitmap blocks that need to be loaded at
> mount time. Note that each decrease in block size increases the number
> of bitmaps fourfold. This is because when the block size is halved, it
> not only doubles the number of blocks, but also halves the capacity of
> each bitmap block.
>
> 4k block size:                          2k block size:
> 10036464 blocks,                        20072928 blocks,
> 307 bitmaps (~= 39 GB)                  1226 bitmaps  (~= 153 GB @ 4k)
> -opin_bitmaps                           -opin_bitmaps
> sb_getblk loop: 0.0s                    sb_getblk loop: 0.3999643s
> ll_rw_block: 1.435871744s               ll_rw_block: 8.143272619s
> wait_on_buffer: 0.513519144s            wait_on_buffer: 1.990925198s
> real    0m4.551s                        real    0m10.906s
> user    0m0.000s                        user    0m0.000s
> sys     0m0.060s                        sys     0m0.028s
>
> -opin_bitmaps,delayed_bitmaps           -opin_bitmaps,delayed_bitmaps
> sb_getblk loop: 0.0s                    sb_getblk loop: 0.3999643s
> ll_rw_block: 1.443871029s               ll_rw_block: 8.944447839s
> real    0m2.128s                        real    0m8.630s
> user    0m0.000s                        user    0m0.000s
> sys     0m0.016s                        sys     0m0.020s
>
> -odyn_bitmaps                           -odyn_bitmaps
> real    0m0.626s                        real    0m0.850s
> user    0m0.000s                        user    0m0.000s
> sys     0m0.008s                        sys     0m0.016s
>
> 1k block size:                          512b block size:
> 40145856 blocks,                        80291712 blocks,
> 4901 bitmaps (~= 612 GB @ 4k)           19603 bitmaps (~= 2.4 TB@4k)
> -opin_bitmaps                           -opin_bitmaps
> sb_getblk loop: 0.19998214s             sb_getblk loop: 0.95991426s
> ll_rw_block: 33.727900516s              ll_rw_block: 110.98165711s
> wait_on_buffer: 1.423872816s            wait_on_buffer: 0.749324905s
> real    0m36.052s                       real    1m51.423s
> user    0m0.000s                        user    0m0.000s
> sys     0m0.124s                        sys     0m0.256s
>
> -opin_bitmaps,delayed_bitmaps           -opin_bitmaps,delayed_bitmaps
> sb_getblk loop: 0.23997856s             sb_getblk loop: 0.95991426s
> ll_rw_block: 33.644994731s              ll_rw_block: 109.427893721s
> real    0m34.562s                       real    1m50.693s
> user    0m0.004s                        user    0m0.004s
> sys     0m0.060s                        sys     0m0.232s
>
> -odyn_bitmaps                           -odyn_bitmaps
> real    0m0.516s                        real    0m0.601s
> user    0m0.000s                        user    0m0.000s
> sys     0m0.004s                        sys     0m0.000s
>
> I will post runtime results of each case early next week.
>
> -Jeff
>
> --
> Jeff Mahoney
> SuSE Labs


  reply	other threads:[~2005-07-09  7:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 21:22 [PATCH] reiserfs: on-demand bitmap loading (testing only) Jeff Mahoney
2005-07-06 22:45 ` Hans Reiser
2005-07-07 16:04   ` Jeff Mahoney
2005-07-07 17:59     ` studdugie
2005-07-07 22:37       ` Pierre Etchemaïté
2005-07-07 23:15         ` David Masover
2005-07-08  4:52           ` Jeffrey Mahoney
2005-07-08  5:52             ` Stefan Traby
2005-07-08 16:55             ` David Masover
2005-07-08 21:41           ` Jeff Mahoney
2005-07-09  7:46             ` Hans Reiser [this message]
2005-07-08  5:35   ` Alexander Zarochentsev
2005-07-08  6:04     ` Stefan Traby

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=42CF80EF.7030204@namesys.com \
    --to=reiser@namesys.com \
    --cc=jeffm@suse.com \
    --cc=ninja@slaphack.com \
    --cc=petchema@concept-micro.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.