linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ali Gholami Rudi <aligrudi@gmail.com>
To: Yu Kuai <yukuai3@huawei.com>
Cc: Yu Kuai <yukuai1@huaweicloud.com>, Xiao Ni <xni@redhat.com>,
	<linux-raid@vger.kernel.org>, <song@kernel.org>
Subject: Re: Unacceptably Poor RAID1 Performance with Many CPU Cores
Date: Wed, 05 Jul 2023 11:29:54 +0330	[thread overview]
Message-ID: <20230507112954@laper.mirepesht> (raw)
In-Reply-To: <a8d9e0e5-d0cc-bed5-8b65-fe9fcc4c7dc4@huawei.com>

Hi,

Yu Kuai <yukuai3@huawei.com> wrote:
> > 
> > On md0 (40GB):
> > READ:  IOPS=1563K BW=6109MiB/s
> > WRITE: IOPS= 670K BW=2745MiB/s
> > 
> > On md3 (14TB):
> > READ:  IOPS=1177K BW=4599MiB/s
> > WRITE: IOPS= 505K BW=1972MiB/s
> > 
> > On md3 but disabling mdadm bitmap (mdadm --grow --bitmap=none /dev/md3):
> > READ:  IOPS=1351K BW=5278MiB/s
> > WRITE: IOPS= 579K BW=2261MiB/s
> 
> Currently, if bitmap is enabled, a bitmap level spinlock will be grabbed
> for each write, and sadly this will require a huge refactor to improve
> performance.

OK.

> > +   95.25%     0.00%  fio      [unknown]               [k] 0xffffffffffffffff
> > +   95.00%     0.00%  fio      fio                     [.] 0x000055e073fcd117
> > +   93.68%     0.13%  fio      [kernel.kallsyms]       [k] entry_SYSCALL_64_after_hwframe
> > +   93.54%     0.03%  fio      [kernel.kallsyms]       [k] do_syscall_64
> > +   92.38%     0.03%  fio      libc.so.6               [.] syscall
> > +   92.18%     0.00%  fio      fio                     [.] 0x000055e073fcaceb
> > +   92.18%     0.08%  fio      fio                     [.] td_io_queue
> > +   92.04%     0.02%  fio      fio                     [.] td_io_commit
> > +   91.76%     0.00%  fio      fio                     [.] 0x000055e073fefe5e
> > -   91.76%     0.05%  fio      libaio.so.1.0.2         [.] io_submit
> >     - 91.71% io_submit
> >        - 91.69% syscall
> >           - 91.58% entry_SYSCALL_64_after_hwframe
> >              - 91.55% do_syscall_64
> >                 - 91.06% __x64_sys_io_submit
> >                    - 90.93% io_submit_one
> >                       - 48.85% aio_write
> >                          - 48.77% ext4_file_write_iter
> >                             - 39.86% iomap_dio_rw
> >                                - 39.85% __iomap_dio_rw
> >                                   - 22.55% blk_finish_plug
> >                                      - 22.55% __blk_flush_plug
> >                                         - 21.67% raid10_unplug
> >                                            - 16.54% submit_bio_noacct_nocheck
> >                                               - 16.44% blk_mq_submit_bio
> >                                                  - 16.17% __rq_qos_throttle
> >                                                     - 16.01% wbt_wait
> 
> You can disable wbt to prevent overhead here.

Very good.  I will give it a try.  And thanks for your time.

Thanks,
Ali


  reply	other threads:[~2023-07-05  8:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  7:54 Unacceptably Poor RAID1 Performance with Many CPU Cores Ali Gholami Rudi
2023-06-15  9:16 ` Xiao Ni
2023-06-15 17:08   ` Ali Gholami Rudi
2023-06-15 17:36     ` Ali Gholami Rudi
2023-06-16  1:53       ` Xiao Ni
2023-06-16  5:20         ` Ali Gholami Rudi
2023-06-15 14:02 ` Yu Kuai
2023-06-16  2:14   ` Xiao Ni
2023-06-16  2:34     ` Yu Kuai
2023-06-16  5:52     ` Ali Gholami Rudi
     [not found]     ` <20231606091224@laper.mirepesht>
2023-06-16  7:31       ` Ali Gholami Rudi
2023-06-16  7:42         ` Yu Kuai
2023-06-16  8:21           ` Ali Gholami Rudi
2023-06-16  8:34             ` Yu Kuai
2023-06-16  8:52               ` Ali Gholami Rudi
2023-06-16  9:17                 ` Yu Kuai
2023-06-16 11:51                 ` Ali Gholami Rudi
2023-06-16 12:27                   ` Yu Kuai
2023-06-18 20:30                     ` Ali Gholami Rudi
2023-06-19  1:22                       ` Yu Kuai
2023-06-19  5:19                       ` Ali Gholami Rudi
2023-06-19  6:53                         ` Yu Kuai
2023-06-21  8:05                     ` Xiao Ni
2023-06-21  8:26                       ` Yu Kuai
2023-06-21  8:55                         ` Xiao Ni
2023-07-01 11:17                         ` Ali Gholami Rudi
2023-07-03 12:39                           ` Yu Kuai
2023-07-05  7:59                             ` Ali Gholami Rudi [this message]
2023-06-21 19:34                       ` Wols Lists
2023-06-23  0:52                         ` Xiao Ni

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=20230507112954@laper.mirepesht \
    --to=aligrudi@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=xni@redhat.com \
    --cc=yukuai1@huaweicloud.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;
as well as URLs for NNTP newsgroup(s).