public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Wang" <00107082@163.com>
To: kent.overstreet@linux.dev
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] bcachefs performance: read is way too slow when a file has no overwrite
Date: Sun, 22 Sep 2024 16:47:25 +0800 (CST)	[thread overview]
Message-ID: <3fcdf5b3.203d.19218ea100b.Coremail.00107082@163.com> (raw)
In-Reply-To: <20240922083148.10070-1-00107082@163.com>


At 2024-09-22 16:31:48, "David Wang" <00107082@163.com> wrote:
>>Hi, 
>>

>btree_io write pattern, collected from btree_node_write_endio, 
>is kind of uniform/flat distributed, not on block-friendly size
>boundaries (I think):
>	+---------+------------+
>	| sectors | percentage |
>	+---------+------------+
>	|    1    |   9.021%   |
>	|    3    |   1.440%   |
>	|    4    |   1.249%   |
>	|    2    |   1.157%   |
>	|    5    |   0.804%   |
>	|    6    |   0.409%   |
>	|    14   |   0.259%   |
>	|    15   |   0.253%   |
>	|    16   |   0.228%   |
>	|    7    |   0.226%   |
>	|    11   |   0.223%   |
>	|    10   |   0.223%   |
>	|    13   |   0.222%   |
>	|    9    |   0.213%   |
>	|    12   |   0.202%   |
>	|    41   |   0.194%   |
>	|    17   |   0.183%   |
>	|    8    |   0.182%   |
>	|    18   |   0.167%   |
>	|    20   |   0.167%   |
>	|    19   |   0.163%   |
>	|    21   |   0.160%   |
>	|   205   |   0.158%   |
>	|    22   |   0.145%   |
>	|    23   |   0.117%   |
>	|    24   |   0.093%   |
>	|    51   |   0.089%   |
>	|    25   |   0.080%   |
>	|   204   |   0.079%   |
>	+---------+------------+
>

Oops...wrong weight used to calculate percentage, it should be
+---------+------------+
| sectors | percentage |
+---------+------------+
|    1    |  45.105%   |
|    3    |   7.200%   |
|    4    |   6.244%   |
|    2    |   5.785%   |
|    5    |   4.018%   |
|    6    |   2.045%   |
|    14   |   1.296%   |
|    15   |   1.264%   |
|    16   |   1.141%   |
|    7    |   1.129%   |
|    11   |   1.117%   |
|    10   |   1.113%   |
|    13   |   1.111%   |
|    9    |   1.065%   |
|    12   |   1.011%   |
|    41   |   0.971%   |
|    17   |   0.913%   |
|    8    |   0.912%   |
|    18   |   0.836%   |
|    20   |   0.835%   |
|    19   |   0.812%   |
|    21   |   0.799%   |
|   205   |   0.791%   |
|    22   |   0.724%   |
|    23   |   0.587%   |
|    24   |   0.465%   |
|    51   |   0.443%   |
|    25   |   0.398%   |
|   204   |   0.396%   |
+---------+------------+


David

  reply	other threads:[~2024-09-22  8:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 15:43 [BUG?] bcachefs performance: read is way too slow when a file has no overwrite David Wang
2024-09-06 17:38 ` Kent Overstreet
2024-09-07 10:34   ` David Wang
2024-09-09 13:37     ` Kent Overstreet
2024-09-12  2:39       ` David Wang
2024-09-12  7:52         ` David Wang
2024-09-21 16:02       ` David Wang
2024-09-21 16:12         ` Kent Overstreet
2024-09-22  1:39           ` David Wang
2024-09-22  8:31             ` David Wang
2024-09-22  8:47               ` David Wang [this message]
2024-09-24 11:08     ` David Wang
2024-09-24 11:30       ` Kent Overstreet
2024-09-24 12:38         ` David Wang

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=3fcdf5b3.203d.19218ea100b.Coremail.00107082@163.com \
    --to=00107082@163.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@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