Thanks for the information. I suspected that was the format. I do notice that I do not always have the block size in the log. I am using version 2.0 and will try a more recent version. It appears that when I set the numjobs parameter the log files will contain the data from each job concatenated. I also notice that the times for each job is not synchronized between jobs. The question is how do I merge the data from each job to consolidate the data? Bill Hooper Micron > -----Original Message----- > From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On > Behalf Of Josh Carter > Sent: Wednesday, February 15, 2012 5:26 PM > To: Bill Hooper (whooper); fio@xxxxxxxxxxxxxxx > Subject: Re: Formats for log files > > Bill, > > Format of entries is: > > time, rate/latency, data direction, block size > > Time: in milliseconds. Bandwidth logs are usually 500 or 1000ms apart; that > can be controlled by the config file with "bwavgtime=[x ms]". > > Rate/latency: for bandwidth, this is in KB/sec. For latency, it's > microseconds. > > Data direction: 0 is read, 1 is write. > > Block size: block size of IOs in bytes. > > For those using R to analyze log files, I have some useful stuff here: > > https://github.com/joshcarter/fio_tools > > In particular, /analysis/fio_log_parsers.R has read_bw_log() and > read_lat_log() functions. > > Best regards, > Josh > > On Feb 15, 2012, at 2:42 PM, Bill Hooper (whooper) wrote: > > > Where can I find documentation for the format of the write_bw_log, > write_iops_log, and write_lat_log output? > > > > Bill Hooper > > Micron > > -- > > 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 > > -- > 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 -- 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
