RE: memory caching

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Things improved but maybe too much :), I was expecting a 100K IOPS not more

server1:~ # fio --name=job --directory=/lvm --size=1G --filesize=1G --iodepth=128 --iodepth_batch_complete=8 --iodepth_batch_submit=8 --ioengine=libaio --direct=1 --numjobs=64 --bs= 4096 --rw=randwrite --group_reporting
Jobs: 50 (f=50): [wwwwww_wwwwwww_wwwwwwwwww_wwwwwwwwwww_www_www_ww_www___ww_w__w_w] [98.3% done] [0K/570.8M /s] [0 /143K iops] [eta 00m:02s]

  write: io=65536MB, bw=584771KB/s, iops=146192 , runt=114761msec

H. Harake

________________________________________
From: Jens Axboe [jaxboe@xxxxxxxxxxxx]
Sent: Tuesday, March 15, 2011 9:28 PM
To: N. Harake
Cc: fio@xxxxxxxxxxxxxxx
Subject: Re: memory caching

On 2011-03-15 13:36, N. Harake wrote:
>
> I noticed when I am using --sync=1, IOPS go down to 15K and throughput to
> 53MB (That¹s horrible for the HW I am using), removing --sync I got 150K
> IOPS and almost 800MB, which make more sense. What does --sync does, and
> hope what I am doing should be enough to avoid any kind of memory caching..
>
> Regards
> H. N. Harake
>
> fio --name=job --directory=/lvm --size=1G --iodepth=1 --sync=1
> --filesize=1G --direct=1 --numjobs=64 --bs=4096 --rw=randwrite
> --group_reporting

If your goal is to maximize iops for testing, use the raw block device.
Use direct=1, and ioengine=libaio. Set depth large, ala:

--iodepth=128 --iodepth_batch_complete=8 --iodepth_batch_submit=8


--
Jens Axboe--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux