RE: fio replay

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

 



Alireza,

I provided the information to show how I ran a replay along with the differences between the original trace and the replay trace with the hope of receiving some advice on what I was doing wrong to cause replay to stop short.

So my interpretation is that something went wrong.  Please help determine what I need to do to use replay correctly.

Eric
-----Original Message-----
From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On Behalf Of Alireza Haghdoost
Sent: Monday, March 03, 2014 9:13 PM
To: Lamkin, Eric
Cc: Jens Axboe; David Nellans; fio@xxxxxxxxxxxxxxx
Subject: Re: fio replay

On Mon, Mar 3, 2014 at 7:25 AM, Lamkin, Eric <Eric.Lamkin@xxxxxxx> wrote:
>
> Comparative analysis replay to original Capture time .88% % reads 
> +1.16% % writes -1.16% Block range 104% Queue operations .78% Blocks 
> queued .78% % sequential queued 108% Max blocks per sequential run 
> 31.4% Completion operations 1.42% Blocks completed .78% % sequential 
> completions 110%


Eric,

Thanks for sharing the results with us. I am interested to hearing your interpretation on this comparison...

--
Alireza
--
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




[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