linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Wang Yugui <wangyugui@e16-tech.com>, Chris Mason <clm@meta.com>
Cc: Christoph Hellwig <hch@lst.de>,
	linux-btrfs@vger.kernel.org, Chris Mason <clm@fb.com>,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: btrfs write-bandwidth performance regression of 6.5-rc4/rc3
Date: Tue, 29 Aug 2023 11:45:28 +0200	[thread overview]
Message-ID: <4108c514-77ff-a247-d6e1-2c12a5dea295@leemhuis.info> (raw)
In-Reply-To: <20230813175032.AA17.409509F4@e16-tech.com>

On 13.08.23 11:50, Wang Yugui wrote:
>> On 8/11/23 10:23 AM, Wang Yugui wrote:
>>>> On Wed, Aug 02, 2023 at 08:04:57AM +0800, Wang Yugui wrote:
>>>>>> And with only a revert of
>>>>>>
>>>>>> "btrfs: submit IO synchronously for fast checksum implementations"?
>>>>> GOOD performance when only (Revert "btrfs: submit IO synchronously for fast
>>>>> checksum implementations") 
>>>> Ok, so you have a case where the offload for the checksumming generation
>>>> actually helps (by a lot).  Adding Chris to the Cc list as he was
>>>> involved with this.
>>>>
>>>>>>> -       if (test_bit(BTRFS_FS_CSUM_IMPL_FAST, &bbio->fs_info->flags))
>>>>>>> +       if ((bbio->bio.bi_opf & REQ_META) && test_bit(BTRFS_FS_CSUM_IMPL_FAST, &bbio->fs_info->flags))
>>>>>>>                 return false;
>>>>>> This disables synchronous checksum calculation entirely for data I/O.
>>>>> without this fix, data I/O checksum is always synchronous?
>>>>> this is a feature change of "btrfs: submit IO synchronously for fast checksum implementations"?
>>>> It is never with the above patch.
>>>>
>>>>>> Also I'm curious if you see any differents for a non-RAID0 (i.e.
>>>>>> single profile) workload.
>>>>> '-m single -d single' is about 10% slow that '-m raid1 -d raid0' in this test
>>>>> case.
>>>> How does it compare with and without the revert?  Can you add the numbers?
>>
>> Looking through the thread, you're comparing -m single -d single, but
>> btrfs is still doing the raid.
>>
>> Sorry to keep asking for more runs, but these numbers are a surprise,
>> and I probably won't have time today to reproduce before vacation next
>> week (sadly, Christoph and I aren't going together).

Sadly I also did not run into either you or Christoph during my own
vacation during the last two weeks. But I'm back from it how, which got
me wondering:

What happened to this regression? Was any progress made to resolve this
in one way or another?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot poke

>> Can you please do a run where lvm or MD raid are providing the raid0?
> no LVM/MD used here.
> 
>> It doesn't look like you're using compression, but I wanted to double check.
> 
> Yes. '-m xx -d yy' with other default mkfs.btrfs option, so no compression.
> 
>> How much ram do you have?
> 
> 192G ECC memory.
> 
> two CPU numa nodes, but all PCIe3 NVMe SSD are connected to one NVMe HBA/
> one numa node.
> 
>> Your fio run has 4 jobs going, can I please see the full fio output for
>> a fast run and a slow run?
> 
> fio results are saved into attachment files (fast.text & slow.txt)
> 
> Best Regards
> Wang Yugui (wangyugui@e16-tech.com)
> 2023/08/13

  reply	other threads:[~2023-08-29  9:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  7:22 btrfs write-bandwidth performance regression of 6.5-rc4/rc3 Wang Yugui
2023-08-01  2:22 ` Wang Yugui
2023-08-01  8:35   ` Christoph Hellwig
2023-08-01  8:56     ` Wang Yugui
2023-08-01  9:03       ` Christoph Hellwig
2023-08-01  9:32         ` Wang Yugui
2023-08-01 10:00           ` Christoph Hellwig
2023-08-01 13:04             ` Wang Yugui
2023-08-01 14:59               ` Christoph Hellwig
2023-08-01 15:51                 ` Wang Yugui
2023-08-01 15:56                   ` Christoph Hellwig
2023-08-01 15:57                     ` Christoph Hellwig
2023-08-02  0:04                     ` Wang Yugui
2023-08-02  9:26                       ` Christoph Hellwig
2023-08-11  8:58                         ` Linux regression tracking (Thorsten Leemhuis)
2023-08-11 10:31                           ` Christoph Hellwig
2023-08-11 14:23                         ` Wang Yugui
2023-08-11 14:52                           ` Chris Mason
2023-08-13  9:50                             ` Wang Yugui
2023-08-29  9:45                               ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-09-11  7:02                                 ` Thorsten Leemhuis
2023-09-11 23:20                                   ` Wang Yugui
2023-09-12  7:58                                     ` Linux regression tracking (Thorsten Leemhuis)
2023-09-26 10:55                                       ` Thorsten Leemhuis
2023-09-26 17:18                                         ` Chris Mason
2023-09-27 11:30                                           ` Linux regression tracking (Thorsten Leemhuis)
2023-12-06 14:22                                 ` Linux regression tracking (Thorsten Leemhuis)
2023-12-13 15:57                                   ` Naohiro Aota
2023-08-02  8:45 ` Linux regression tracking #adding (Thorsten Leemhuis)

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=4108c514-77ff-a247-d6e1-2c12a5dea295@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=clm@fb.com \
    --cc=clm@meta.com \
    --cc=hch@lst.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=wangyugui@e16-tech.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;
as well as URLs for NNTP newsgroup(s).