Digital Marketing

How to examine the performance behavior of AWS EFS file system


$ sudo fio --name=fio-efs --filesize=10G --filename=./efs/fio-efs-test.img --bs=1M --nrfiles=1 --direct=1 --sync=0 --rw=write --iodepth=200 --ioengine=libaio
fio-efs: (g=0): rw=write, bs=1M-1M/1M-1M/1M-1M, ioengine=libaio, iodepth=200
fio-2.1.5
Starting 1 process
fio-efs: Laying out IO file(s) (1 file(s) / 10240MB)
Jobs: 1 (f=1): [W] [98.1% done] [0KB/0KB/0KB /s] [0/0/0 iops] [eta 00m:06s]     
fio-efs: (groupid=0, jobs=1): err= 0: pid=8292: Wed Aug 16 18:21:06 2017
  write: io=10240MB, bw=34459KB/s, iops=33, runt=304294msec
    slat (usec): min=52, max=212, avg=87.60, stdev=13.28
    clat (msec): min=38, max=26291, avg=5941.21, stdev=5225.86
     lat (msec): min=38, max=26291, avg=5941.30, stdev=5225.86
    clat percentiles (msec):
     |  1.00th=[ 1123],  5.00th=[ 2089], 10.00th=[ 2114], 20.00th=[ 2212],
     | 30.00th=[ 2311], 40.00th=[ 2442], 50.00th=[ 2704], 60.00th=[ 3097],
     | 70.00th=[12125], 80.00th=[13173], 90.00th=[13173], 95.00th=[13173],
     | 99.00th=[16712], 99.50th=[16712], 99.90th=[16712], 99.95th=[16712],
     | 99.99th=[16712]
    bw (KB  /s): min=  602, max=104239, per=100.00%, avg=35875.43, stdev=31200.90
    lat (msec) : 50=0.01%, 100=0.04%, 250=0.12%, 500=0.24%, 750=0.24%
    lat (msec) : 1000=0.24%, 2000=0.95%, >=2000=98.15%
  cpu          : usr=0.06%, sys=0.28%, ctx=15282, majf=0, minf=8
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.2%, 32=0.3%, >=64=99.4%
     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    : total=r=0/w=10240/d=0, short=r=0/w=0/d=0
     latency   : target=0, window=0, percentile=100.00%, depth=200

Run status group 0 (all jobs):
  WRITE: io=10240MB, aggrb=34459KB/s, minb=34459KB/s, maxb=34459KB/s, mint=304294msec, maxt=304294msec

Comments

Popular posts from this blog

MySQL Sandbox with the Sakila sample database