From: Yusuf Hadiwinata <[email protected]>
To: Ammar Faizi <[email protected]>, Support <[email protected]>
Cc: Ammar Rafli Arkan <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Paber Panjaitan <[email protected]>
Subject: Re: [## 385523 ##] Disk I/O di Neo Lite kembali bermasalah
Date: Fri, 12 Jul 2024 13:12:29 +0000 [thread overview]
Message-ID: <KL1PR06MB66702E7ADAF833A1D567BAC7B6A62@KL1PR06MB6670.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <KL1PR06MB6670A3EF38441C894B3AF19BB6A62@KL1PR06MB6670.apcprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 11167 bytes --]
Dear Ammar dan Team
Sorry setelah kita cek IP 103.175.218.159 tidak di host yang kita suspect, mohon ignore email sebelumnya
Kita coba analisa lagi ya
thnks
________________________________
From: Yusuf Hadiwinata <[email protected]>
Sent: Friday, 12 July 2024 20:06
To: Ammar Faizi <[email protected]>; Support <[email protected]>
Cc: Ammar Rafli Arkan <[email protected]>; Alviro Iskandar Setiawan <[email protected]>; GNU/Weeb Mailing List <[email protected]>; Paber Panjaitan <[email protected]>
Subject: Re: [## 385523 ##] Disk I/O di Neo Lite kembali bermasalah
Dear Ammar dan Team
Kita mau analisa beberapa suspect di Host yang terdapat instance yang di laporkan, boleh kita move instance nya ? Akan ada downtime estimas < 5 menit jika berkenan
Kalo ada preferensi waktu boleh di info juga kira2 enak nya jam berapaan
Thanks
________________________________
From: Ammar Faizi <[email protected]>
Sent: Friday, 12 July 2024 19:42
To: Support <[email protected]>
Cc: Ammar Rafli Arkan <[email protected]>; Yusuf Hadiwinata <[email protected]>; Alviro Iskandar Setiawan <[email protected]>; GNU/Weeb Mailing List <[email protected]>; Paber Panjaitan <[email protected]>
Subject: Re: [## 385523 ##] Disk I/O di Neo Lite kembali bermasalah
On Fri, Jul 12, 2024 at 05:23:09AM -0700, Ammar Rafli wrote:
> Silakan untuk melampirkan capture hasil fio nya pada ticket ini agar kami dapat melihat me-review detail IOPS nya ya Pak.
Saya lampirkan output fio berikut:
root@wjv001:~/fio# ./fio --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --rw=read --filename=/root/fio --bs=8k --iodepth=256 --size=2Gb --runtime=60 --numjobs=4 --time_based --rwmixread=75 --group_reporting
fio: engine libaio not loadable
fio: failed to load engine
# Note: libaio tidak available, saya ubah ke io_uring.
root@wjv001:~/fio# ./fio --ioengine=io_uring --direct=1 --gtod_reduce=1 --name=test --rw=read --filename=./test --bs=8k --iodepth=256 --size=2Gb --runtime=60 --numjobs=4 --time_based --rwmixread=75 --group_reporting
test: (g=0): rw=read, bs=(R) 8192B-8192B, (W) 8192B-8192B, (T) 8192B-8192B, ioengine=io_uring, iodepth=256
...
fio-3.37-60-g6eaa64
Starting 4 processes
Jobs: 2 (f=2): [_(2),R(2)][34.3%][r=5853KiB/s][r=731 IOPS][eta 01m:59s]
test: (groupid=0, jobs=4): err= 0: pid=18651: Fri Jul 12 19:25:53 2024
read: IOPS=1001, BW=8013KiB/s (8205kB/s)(477MiB/60951msec)
bw ( KiB/s): min= 96, max=20864, per=100.00%, avg=8536.02, stdev=1493.19, samples=385
iops : min= 12, max= 2608, avg=1066.99, stdev=186.65, samples=385
cpu : usr=0.11%, sys=0.25%, ctx=70031, majf=0, minf=2066
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.2%, >=64=99.6%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
issued rwts: total=61048,0,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=256
Run status group 0 (all jobs):
READ: bw=8013KiB/s (8205kB/s), 8013KiB/s-8013KiB/s (8205kB/s-8205kB/s), io=477MiB (500MB), run=60951-60951msec
Disk stats (read/write):
sda: ios=60990/53, sectors=976152/528, merge=0/10, ticks=55711072/42055, in_queue=55753611, util=99.96%
=============================================================================================================
root@wjv001:~/fio# ./fio --ioengine=io_uring --direct=1 --gtod_reduce=1 --name=test --rw=rw --filename=./test --bs=8k --iodepth=256 --size=2Gb --runtime=60 --numjobs=4 --time_based --rwmixread=50 --group_reporting
test: (g=0): rw=rw, bs=(R) 8192B-8192B, (W) 8192B-8192B, (T) 8192B-8192B, ioengine=io_uring, iodepth=256
...
fio-3.37-60-g6eaa64
Starting 4 processes
Jobs: 4 (f=4): [M(4)][100.0%][r=8032KiB/s,w=8104KiB/s][r=1004,w=1013 IOPS][eta 00m:00s]
test: (groupid=0, jobs=4): err= 0: pid=18664: Fri Jul 12 19:31:16 2024
read: IOPS=994, BW=7959KiB/s (8150kB/s)(471MiB/60624msec)
bw ( KiB/s): min= 448, max=21488, per=99.84%, avg=7947.47, stdev=1237.33, samples=481
iops : min= 56, max= 2686, avg=993.41, stdev=154.67, samples=481
write: IOPS=1001, BW=8010KiB/s (8202kB/s)(474MiB/60624msec); 0 zone resets
bw ( KiB/s): min= 416, max=21520, per=99.71%, avg=7987.95, stdev=1227.20, samples=481
iops : min= 52, max= 2690, avg=998.47, stdev=153.40, samples=481
cpu : usr=0.20%, sys=0.46%, ctx=96868, majf=0, minf=26
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=99.8%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
issued rwts: total=60316,60700,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=256
Run status group 0 (all jobs):
READ: bw=7959KiB/s (8150kB/s), 7959KiB/s-7959KiB/s (8150kB/s-8150kB/s), io=471MiB (494MB), run=60624-60624msec
WRITE: bw=8010KiB/s (8202kB/s), 8010KiB/s-8010KiB/s (8202kB/s-8202kB/s), io=474MiB (497MB), run=60624-60624msec
Disk stats (read/write):
sda: ios=60146/60471, sectors=962336/967448, merge=0/12, ticks=27376373/30599469, in_queue=57977062, util=99.97%
=============================================================================================================
root@wjv001:~/fio# ./fio --ioengine=io_uring --direct=1 --gtod_reduce=1 --name=test --rw=randread --filename=./test --bs=8k --iodepth=256 --size=2Gb --runtime=60 --numjobs=4 --time_based --rwmixread=100 --group_reporting
test: (g=0): rw=randread, bs=(R) 8192B-8192B, (W) 8192B-8192B, (T) 8192B-8192B, ioengine=io_uring, iodepth=256
...
fio-3.37-60-g6eaa64
Starting 4 processes
Jobs: 2 (f=2): [r(1),_(1),r(1),_(1)][34.3%][r=5904KiB/s][r=738 IOPS][eta 01m:59s]
test: (groupid=0, jobs=4): err= 0: pid=18673: Fri Jul 12 19:35:08 2024
read: IOPS=1001, BW=8013KiB/s (8206kB/s)(478MiB/61139msec)
bw ( KiB/s): min= 1824, max=18288, per=100.00%, avg=8101.39, stdev=1076.94, samples=445
iops : min= 228, max= 2286, avg=1012.67, stdev=134.62, samples=445
cpu : usr=0.12%, sys=0.26%, ctx=71964, majf=0, minf=2076
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.2%, >=64=99.6%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
issued rwts: total=61240,0,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=256
Run status group 0 (all jobs):
READ: bw=8013KiB/s (8206kB/s), 8013KiB/s-8013KiB/s (8206kB/s-8206kB/s), io=478MiB (502MB), run=61139-61139msec
Disk stats (read/write):
sda: ios=61240/7, sectors=980080/112, merge=0/7, ticks=61595911/6429, in_queue=61602360, util=99.95%
=============================================================================================================
root@wjv001:~/fio# ./fio --ioengine=io_uring --direct=1 --gtod_reduce=1 --name=test --rw=randwrite --filename=./test --bs=8k --iodepth=256 --size=2Gb --runtime=60 --numjobs=4 --time_based --rwmixread=75 --group_reporting
test: (g=0): rw=randwrite, bs=(R) 8192B-8192B, (W) 8192B-8192B, (T) 8192B-8192B, ioengine=io_uring, iodepth=256
...
fio-3.37-60-g6eaa64
Starting 4 processes
Jobs: 4 (f=4): [w(4)][3.5%][w=1936KiB/s][w=242 IOPS][eta 28m:31s]
test: (groupid=0, jobs=4): err= 0: pid=18683: Fri Jul 12 19:37:33 2024
write: IOPS=1001, BW=8010KiB/s (8202kB/s)(478MiB/61102msec); 0 zone resets
bw ( KiB/s): min= 96, max=27984, per=100.00%, avg=8245.91, stdev=1833.66, samples=465
iops : min= 12, max= 3498, avg=1030.70, stdev=229.20, samples=465
cpu : usr=0.13%, sys=0.27%, ctx=44021, majf=0, minf=28
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.2%, >=64=99.6%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
issued rwts: total=0,61176,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=256
Run status group 0 (all jobs):
WRITE: bw=8010KiB/s (8202kB/s), 8010KiB/s-8010KiB/s (8202kB/s-8202kB/s), io=478MiB (501MB), run=61102-61102msec
Disk stats (read/write):
sda: ios=0/60981, sectors=0/975608, merge=0/11, ticks=0/52000246, in_queue=52001504, util=99.95%
=============================================================================================================
root@wjv001:~/fio# ./fio --ioengine=io_uring --direct=1 --gtod_reduce=1 --name=test --rw=randrw --filename=./test --bs=8k --iodepth=256 --size=2Gb --runtime=60 --numjobs=4 --time_based --rwmixread=0 --group_reporting
test: (g=0): rw=randrw, bs=(R) 8192B-8192B, (W) 8192B-8192B, (T) 8192B-8192B, ioengine=io_uring, iodepth=256
...
fio-3.37-60-g6eaa64
Starting 4 processes
Jobs: 4 (f=4): [w(4)][100.0%][w=6904KiB/s][w=863 IOPS][eta 00m:00s]
test: (groupid=0, jobs=4): err= 0: pid=18693: Fri Jul 12 19:39:00 2024
write: IOPS=1001, BW=8009KiB/s (8201kB/s)(476MiB/60853msec); 0 zone resets
bw ( KiB/s): min= 256, max=24624, per=100.00%, avg=8209.34, stdev=1657.90, samples=470
iops : min= 32, max= 3078, avg=1026.15, stdev=207.24, samples=470
cpu : usr=0.15%, sys=0.31%, ctx=49963, majf=0, minf=28
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.2%, >=64=99.6%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
issued rwts: total=0,60920,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=256
Run status group 0 (all jobs):
WRITE: bw=8009KiB/s (8201kB/s), 8009KiB/s-8009KiB/s (8201kB/s-8201kB/s), io=476MiB (499MB), run=60853-60853msec
Disk stats (read/write):
sda: ios=0/60744, sectors=0/971808, merge=0/12, ticks=0/56919694, in_queue=56920300, util=99.97%
=============================================================================================================
--
Ammar Faizi
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
[-- Attachment #2: Type: text/html, Size: 18057 bytes --]
next prev parent reply other threads:[~2024-07-12 13:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 11:12 Disk I/O di Neo Lite kembali bermasalah Ammar Faizi
2024-07-12 11:27 ` Re:[## 385523 ##] " Ammar Rafli
2024-07-12 11:34 ` [## " Ammar Faizi
2024-07-12 11:40 ` Ammar Rafli
2024-07-12 11:47 ` [## " Ammar Faizi
2024-07-12 11:57 ` Ammar Rafli
2024-07-12 12:09 ` [## " Ammar Faizi
2024-07-12 12:20 ` Ammar Rafli
2024-07-12 12:23 ` Ammar Rafli
2024-07-12 12:42 ` [## " Ammar Faizi
2024-07-12 13:00 ` Ammar Rafli
2024-07-12 13:19 ` [## " Ammar Faizi
2024-07-12 13:06 ` Yusuf Hadiwinata
2024-07-12 13:12 ` Yusuf Hadiwinata [this message]
2024-07-12 13:13 ` Ammar Faizi
2024-07-12 13:20 ` Yusuf Hadiwinata
2024-07-12 13:21 ` Ammar Faizi
2024-07-12 13:31 ` Yusuf Hadiwinata
2024-07-12 13:40 ` Ammar Faizi
2024-07-12 14:12 ` Ammar Rafli
2024-07-12 14:45 ` [## " Yusuf Hadiwinata
2024-07-12 13:12 ` Ammar Faizi
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=KL1PR06MB66702E7ADAF833A1D567BAC7B6A62@KL1PR06MB6670.apcprd06.prod.outlook.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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