On Tue, Jun 25 2013, Erwan Velu wrote: > Hey Jens, > > I'm been using fio for years and that's a wonderful tool. Since I'm working > at eNovance, I'm facing situations where I shall compare servers and disks > in a clusterized environnement. > > In my last case, I had 6 servers with 33 disks each leading to a serious > problem. How can I test and visualize performances in various io pattern : > - read, write, randread, randwrite > - 4k, 128k, 1m block size > - one disk after the other (to estimate the performance of each disk helping > tracking the weaks) > - all the disks at the same time (to estimate the ability of the host to > manage all disks at the same time) > > To help setting up this benchmark, I've been doing two tools : > - genfio to generate the fio script files > Details of its behavior & options can be found in the commit itself (also > available with the -help option) > A single command like 'genfio -d sdb,sdc,sdd,sde -a -b 4k,128k,1m -r 100' > generates a single fio file that will runs 60 tests on 4 disks during 100 > seconds each. That does avoid human mistake and ease reproductability > > https://github.com/enovance/fio/commit/ca0ede58c1ca10469d9937110c3faa30ce88ca1f > > - fio2gnuplot turns the output log from fio into gnuplot traces > It does help tracing many log files in a friendly way by using 3D graphs (to > avoid 2D overlapping) or generates several histograms to compare > min/max/avg/stddev of some selected outputfile. If outputfiles > are well named (like if you use genfio) you can use regexp to select the > files you want to graph. > You can so select logs by the io pattern, the name of disk, etc... > More details in the commit or in the --help option > https://github.com/enovance/fio/commit/1fa4c6436b31b71ab2bb373a5033a62bca47bce0 > > I've been uploading some sample output here : > http://www.flickr.com/photos/ennael/sets/72157634249027122/ > > In a fraction of seconds, you are able to visualize the global performances > with the 3D graph and compared values betweens runs by using the histograms. > On a real 6 servers, 197 disks (33 each), it helped at detecting the weak > devices very quickly. > > I hope this work will have some interest for the fio project or maybe some > other users. > > This two tools are available on my 'tools' branch of my github repository. > It's on top the current master so very easy to merge. Both tools are > splitted in two commits. > > https://github.com/enovance/fio/tree/tools Nifty stuff! Thanks, I'll take a look at it and get it integrated. -- 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
