Home | History | Annotate | Download | only in doc

Lines Matching refs:One

92     containing parallel trace streams -- one file per CPU per
94 files into one time-ordered stream of traces for all devices.
159 of IOs during the run\footnote{One of the areas that needs some
161 IOs during a run. In theory, one would like ${Q2I} + {I2D} + {D2C}
290 In this subsection one can see the average number of IOs on the request
314 This table and the preceding one have to be considered together --
315 in the sample output in the immediately preceding table one can see
349 In addition to the default sections output, if one supplies the
360 One must be aware, however, that the process ID may not have anything
536 Using this, one is then able to plot regions of activity versus
537 inactivity -- and one can gather a sense of deltas between the queueing
556 are one-for-one for sizes up to 1,024 blocks in the IO, and then a
561 representing sizes $\ge 1024$ blocks. (This is done so that one can
572 this, one can quickly discern some different characteristics between
573 the 3 runs -- in particular, one can see that there is only a single
587 Y axis for this chart.}. Again, visually, one can see that the black
589 out. And then one can make the broad generalization of higher reds,
679 provide per-IO latency information, one for queue time (Q2D), one
680 for total IO time (Q2C) and one for latencies induced by lower layer
709 \item One of the following characters:
750 The seek difference is calculated in one of two ways:
836 seek distances based solely upon the ending block address of one IO,
873 allowing one to change that granularity. The smaller the value, the
879 the traces parsed. With this option, one can reduce the analysis to
880 one or more devices provided in the string passed to this option. The
888 found in the traces. With this option, one can specify which processes
924 being measured can have up to 2 files output: One with Q2Q information
925 and one with D2D seek information. Information on the output produced
978 The normal \texttt{iostat} command allows one to specify the snapshot
979 interval, likewise, \texttt{btt} allows one to specify how many seconds
992 These options allow one to dictate to \texttt{btt} when to start and stop
1127 mode after the image is produced. In this interactive mode one can enter