Lines Matching full:time
94 files into one time-ordered stream of traces for all devices.
108 \item[average component times across all IOs] The time line of each IO
112 \item Time needed to insert or merge an incoming IO onto the request
113 queue. This is the average time from when the IO enters the block
116 This is denoted as \emph{Q2I} time.
119 occasion there are also some time spent \emph{sleeping} waiting
124 \item[Q2G] Time needed to \emph{get} a request (get request
127 \item[G2I] Time needed to put that request onto the request
133 amount of time between the queue trace and the merge trace.
135 \item Time spent on the request queue. The average time from when
139 Referred to as \emph{I2D} time\footnote{The \emph{issue} trace
144 \item Driver and device time -- the average time from when the
148 This is referred to as the \emph{D2C} time\
154 \item \emph{Q2Q} which measures the time between queue traces
190 as to where IO spend most of the time on average. The following output
191 shows the percentage of time spent in each of the phases of an
270 DEV | # Plugs # Timer Us | % Time Q Plugged
291 queue at the time of an unplug or unplug due to a timeout. The following
297 DEV | # Plugs # Timer Us | % Time Q Plugged
302 Overall | # Plugs # Timer Us | % Time Q Plugged
357 of the time line discussed above on page~\pageref{tl-defs}, a chart is
383 will also break down the various parts of an IOs time line based upon a
407 time in seconds, as in:
472 histogram output for the amount of IOs released at unplug time.
479 those periods of time when queue and complete traces are being
488 points are presented with the first column (X values) being the time
549 low, it represents an extended period of time where no queue requests
621 \texttt{btt} can produce a text file containing time line data for each
622 IO processed. The time line data contains rudimentary information for
669 \item Time of the trace (seconds from the start of the run)
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
685 command at that time (either Q2D, D2C or Q2C).
768 first column will contain a time value (seconds), and the second column
772 \texttt{btt} will just output the time value for the point, and the
775 value is the number of seeks present at that time.
779 in that time frame, then:
782 \item[column 1] Midway point in time for this span, or: \hfill$\alpha +
824 [ -t <sec> | --time-start=<sec> ]
825 [ -T <sec> | --time-end=<sec> ]
855 output, first column is time (seconds), second is the block number,
859 output, first column is time (seconds), second is the block number,
863 and write) are output, first column is time (seconds), second is
952 time values are separated from the Q time values with a vertical bar.
962 name as a base) which contains: A time stamp in the first column,
984 \subsection{\label{sec:o-tT}\texttt{--time-start}/\texttt{-t} and
985 \texttt{--time-end}/\texttt{T}}
989 not always consistent at this point in time.}
994 trace chosen will be between the start time (or 0.0 if not
995 specified) and end time (or the end of the run) specified.
1032 rate (number of thousands of traces per second), and the real time for
1035 each time):
1121 display will display \emph{each} IO generated, with the time (seconds)
