Re: BTRFS Benchmarking

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

 



Hi,

I uploaded the PDF on Dropbox that does not require login
https://www.dropbox.com/s/5i8l0kmdutxj6pb/sysbench-sas3t-btrfs1.pdf


>   Can you tell us what the unit of the Y-axis is? Is it MB/s or IOPs
> or time for a fixed amount data or... ?
Unit is MB/s ;
For each test, I gather speed every second.
So for a particular test, there is 60 dots (for example, speed for
BTRFS on 1 thread, blocksize=512b, sequential read).
As 60 dots are not easy to read, I created second pages with one
aggregated value as 95 percentile.

Sequential read results seems heavily altered by Linux pagecache. I
wondered what would be the exact methodology to disable this
optimization.
But all FS were run in the exact same behaviour (bash scripted with
umount / mount after each session).


I provided access to the bash script I used and R script to create nice PDF.
Feel free to give me any feedback on how I could get results more accurate.

https://github.com/odoucet/fs-benchs


>   For example, in the seqwr/512 test, is btrfs doing really well at
> small numbers of threads, getting steadily worse, or is it doing
> really badly, and improves hugely as the number of threads goes up?

It is doing badly but improves when number of threads goes up.


I'll improve my benchmark results by adding self-explainable legends.
I will be happy to discuss my methodology if you think something is
wrong.


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


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux