All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lego Lin <lego.lin at gmail.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: iSCSI Sequential Read with BS 128K Performance
Date: Fri, 18 Dec 2020 16:11:32 +0800	[thread overview]
Message-ID: <CALR1AzKiJiqs7f_c0hN5aKXaKKWiVAev30OqAq6VegjL00Y_Yw@mail.gmail.com> (raw)
In-Reply-To: CALR1Az+MZo2s0GYZcZaUyvzPy=fuUHgtsXFHRdiKvHnubmOZ8g@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 2448 bytes --]

Hi, all:

Sorry for previous email that miss 1 thing: I test performance with SPDK
NULL Block Device

On Fri, Dec 18, 2020 at 4:09 PM Lego Lin <lego.lin(a)gmail.com> wrote:

> Hi, all:
> I just tested SPDK 20.10.x iSCSI performance and I got
> following performance data: (All Testing with FIO QD 32)
> [OK] (100%RndR_4K,   100%RndW_4K)   : (read: IOPS=155k, BW=605MiB/s
> (634MB/s),   write: IOPS=140k, BW=547MiB/s (573MB/s))
> [OK] (100%RndR_8K,   100%RndW_8K)   : (read: IOPS=147k, BW=1152MiB/s
> (1208MB/s), write: IOPS=128k, BW=1003MiB/s (1051MB/s))
> [NOK] (100%SeqR_128K, 100%SeqW_128K) : (read: IOPS=210, BW=26.3MiB/s
> (27.5MB/s),  write: IOPS=14.6k, BW=1831MiB/s (1920MB/s))
> => Read Bad, Write OK
> [NOK] (100%SeqR_32K,  100%SeqR_16K)  : (read: IOPS=9418, BW=294MiB/s
> (309MB/s),   read: IOPS=105k, BW=1641MiB/s (1721MB/s))
> => [NOK] BS_32K + QD_32
> => [OK]  BS_16K + QD_32
> [OK] (100%SeqR_8K,   100%SeqR_4K)   : (read: IOPS=149k, BW=1160MiB/s
> (1217MB/s), read: IOPS=157k, BW=612MiB/s (642MB/s))
>
> Focus on BS 128K
> [OK] QD1: read: IOPS=5543, BW=693MiB/s (727MB/s)
> [OK] QD8: read: IOPS=21.1k, BW=2634MiB/s (2762MB/s)
> [NOK] QD16: read: IOPS=301, BW=37.7MiB/s (39.5MB/s)
>
> FIO Configuration:
> ioengine=libaio
> direct=1
> numjobs=1
>
> I also check with document:
> https://ci.spdk.io/download/performance-reports/SPDK_tcp_perf_report_2007.pdf
> Inside this document, it also suggest Sequential Read test with BS=128K +
> QD8
>
> I think the low performance with BS=128K + QD32 should not relate to
> iSCSI, but can anyone share experience about tuning iSCSI sequential read
> performance? It's weird that performance drop with high QD. Any suggestion
> are welcome.
>
> Thanks
>
> Following are my test configuration
> 1. Network bandwidth: 40GB
> 2. TCP Setting at both target and client
>     tcp_timestamps: "1"
>     tcp_sack: "0",
>     tcp_rmem: "4096 87380 134217728"
>     tcp_wmem: "4096 87380 134217728",
>     tcp_mem: "4096 87380 134217728",
>     rmem_default: "524287",
>     wmem_default: "524287",
>     rmem_max: "268435456",
>     wmem_max: "268435456",
>     optmem_max: "268435456",
>     netdev_max_backlog: "300000"}
> 3. number of CPU cores at target and client: 48 vcores
>      Intel(R) Xeon(R) Silver 4215 CPU @ 2.50GHz * 2
> 4. disable irqbalance / enable CPU power government
> 5. run SPDK with: ./iscsi_tgt -m 0x08007C08007C
>

             reply	other threads:[~2020-12-18  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18  8:11 Lego Lin [this message]
2020-12-22  5:46 [SPDK] Re: iSCSI Sequential Read with BS 128K Performance Yang, Ziye
2020-12-23  2:16 Yang, Ziye
2020-12-23 14:19 Lego Lin
2020-12-28  3:03 Yang, Ziye

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=CALR1AzKiJiqs7f_c0hN5aKXaKKWiVAev30OqAq6VegjL00Y_Yw@mail.gmail.com \
    --to=spdk@lists.01.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 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.