mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yu Kuai <yukuai1@huaweicloud.com>
To: "Dragan Milivojević" <galileo@pkm-inc.com>,
	"Yu Kuai" <yukuai1@huaweicloud.com>,
	"yukuai (C)" <yukuai3@huawei.com>
Cc: Song Liu <song@kernel.org>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	yi.zhang@huawei.com, yangerkun@huawei.com, "Luse,
	Paul E" <paul.e.luse@intel.com>
Subject: Re: [PATCH md-6.13] md: remove bitmap file support
Date: Wed, 13 Nov 2024 09:18:14 +0800	[thread overview]
Message-ID: <adae6bff-8401-b641-438c-d212b20a7430@huaweicloud.com> (raw)
In-Reply-To: <e32688e7-310e-49fc-9f52-44dd183f9666@pkm-inc.com>

Hi,

在 2024/11/11 22:07, Dragan Milivojević 写道:
> Reads are fine but writes are many times slower ...
> 
> 
>>
>> I still can't believe your test result, and I can't figure out why
>> internal bitmap is so slow. Hence I use ramdisk(10GB) to create a raid5,
>> and use the same fio script to test, the result is quite different from
>> yours:
>>
>> ram0:            981MiB/s
>> non-bitmap:        132MiB/s
>> internal-bitmap:    95.5MiB/s
>>>

So, I waited for Paul to have a chance to give it a test for real disks,
still, results are similar to above.
> 
> I don't know, I can provide full fio test logs including fio "tracing" 
> for these iodepth 8
> tests if that would make any difference.
> 

No, I don't need fio logs.
> 
> 
>> There is absolutely something wrong here, it doesn't make sense to me
>> that internal bitmap is so slow. However, I have no idea until you can
>> provide the perf result.
> 
> I may be able to find time to do that over the weekend, but don’t hold 
> me to it.
> The test setup will not be the same, server is in production ...
> I did leave some "spare" partitions on all drives to investigate this 
> issue further
> but did not find the time.
> 
> Please send me an example of how would you like me to run the perf tool, 
> I haven't used
> it much.

You can see examples here:

https://github.com/brendangregg/FlameGraph

To be short, while test is running:

perf record -a -g -- sleep 10
perf script -i perf.data | ./stackcollapse-perf.pl | ./flamegraph.pl

BTW, you said that you're using production environment, this will
probably make it hard to analyze performance.

Thanks,
Kuai


  reply	other threads:[~2024-11-13  1:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 12:59 Yu Kuai
2024-11-07 23:41 ` Song Liu
2024-11-08  1:03   ` Yu Kuai
2024-11-08  1:28     ` Song Liu
2024-11-08  1:33       ` Yu Kuai
2024-11-08  5:15       ` Dragan Milivojević
2024-11-08  6:07         ` Yu Kuai
2024-11-08 22:19           ` Dragan Milivojević
2024-11-09  1:43             ` Yu Kuai
2024-11-09  2:15               ` Dragan Milivojević
2024-11-11  2:04                 ` Yu Kuai
2024-11-11 11:59                   ` Dragan Milivojević
2024-11-11 13:02                     ` Yu Kuai
2024-11-11 14:07                       ` Dragan Milivojević
2024-11-13  1:18                         ` Yu Kuai [this message]
2024-11-13  1:25                           ` Dragan Milivojević
2024-11-12  7:54       ` Mariusz Tkaczyk

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=adae6bff-8401-b641-438c-d212b20a7430@huaweicloud.com \
    --to=yukuai1@huaweicloud.com \
    --cc=galileo@pkm-inc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=paul.e.luse@intel.com \
    --cc=song@kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®