Lines Matching refs:Values
217 issued requests (D) and the resultant ratio. We also provide values
238 between IOs. Values provided include the number of seeks (number of IOs
243 The first of the two sections displays values for Q2Q seek distances --
255 We have almost exclusively seen median and mode values of 0, indicating
316 how the larger number of data values for device (8,0) dominates in
478 The activity data file contains a series of data values that indicate
480 processed. The values happen to be in a format easily handled by
488 points are presented with the first column (X values) being the time
489 (in seconds), and the second column (Y values) providing an on/off
490 type of setting. For each pair, the Y values have two settings off
564 The first column (X values) is the various IO sizes, and the second
565 column (Y values) represents the number of IOs of that size.
683 In both cases, the first column (X values) represent runtime (seconds),
684 while the second column (Y values) shows the actual latency for a
720 The format of the data is to have the runtime values (seconds since
721 the start of the run) in column 1 (X values); and the difference in
722 sectors from the previous IO in column 2 (Y values). Here is a snippet
872 of each other. The default values is 0.1 seconds; with this option
952 time values are separated from the Q time values with a vertical bar.
1002 number of IOs released. There are 21 output values into the file, as
1029 granularity) values describing the progress it is making through the
1057 The format is space-delimited values starting with a 3-character
1060 fields representing data values. The following table shows the record
