LTTNG-IOLATENCYTOP(1)
π LTTNG-IOLATENCYTOP π
okay bestie, gather round, because this is lttng-iolatencytop β the LTTng analyses IO latency top tool, living in the User Commands section of your manual, and she is serving.
β¨ NAME β¨
lttng-iolatencytop β LTTng analyses IO latency top. that's it, that's the whole vibe. the I/O command. π¦
πΈ DESCRIPTION πΈ
so the usage goes a little something like this, and yes you're gonna want to read the whole thing because there are so many flags:
usage: lttng-iolatencytop [-h] [-r REFRESH] [--gmt] [--skip-validation]
[--begin BEGIN] [--end END] [--period PERIOD]
[--period-captures PERIOD_CAPTURES] [--period-begin PERIOD_BEGIN]
[--period-end PERIOD_END] [--period-begin-key PERIOD_BEGIN_KEY]
[--period-end-key PERIOD_END_KEY] [--period-key-value
PERIOD_KEY_VALUE] [--cpu CPU] [--timerange TIMERANGE]
[--progress-use-size] [--no-intersection] [-V] [--debug]
[--no-color] [--no-progress] [--min MIN] [--max MAX] [--log]
[--limit LIMIT] [--top] [--stats] [--freq] [--freq-resolution
FREQ_RESOLUTION] [--freq-uniform] [--freq-series] [--usage]
[--minsize MINSIZE] [--maxsize MAXSIZE] <path/to/trace>
π positional arguments π
<path/to/trace>β the trace path, babe. that's where your trace lives. point her at it. π
π§ optional arguments π§
-h,--helpβ shows this help message and then dips. show this help message and exit. iconic behaviour honestly.-r REFRESH,--refresh REFRESHβ Refresh period, with optional units suffix (default units:s). so if you don't say a unit she's gonna assume seconds, periodt.--gmtβ Manipulate timestamps based on GMT instead of local time. timezone girlie hours π--skip-validationβ Skip the trace validation. no vibe check for the trace today, we trust her π--begin BEGINβ start time:hh:mm:ss[.nnnnnnnnn]--end ENDβ end time:hh:mm:ss[.nnnnnnnnn]--period PERIODβ Period definition--period-captures PERIOD_CAPTURESβ Period captures definition--period-begin PERIOD_BEGINβ Analysis period start marker event name--period-end PERIOD_ENDβ Analysis period end marker event name (requires--period-begin). yeah she's not optional-optional, you need the begin one too, no cap.--period-begin-key PERIOD_BEGIN_KEYβ Optional, list of event field names used to match period markers (default:cpu_id)--period-end-key PERIOD_END_KEYβ Optional, list of event field names used to match period marker. If none specified, use the same--period-begin-key. she's a copycat and we love that for her π--period-key-value PERIOD_KEY_VALUEβ Optional, define a fixed key value to which a period must correspond to be considered.--cpu CPUβ Filter the results only for this list of CPU IDs. pick your fave cores π--timerange TIMERANGEβ time range:[begin,end]--progress-use-sizeβ use trace size to approximate progress--no-intersectionβ disable stream intersection mode-V,--versionβ show program's version number and exit--debugβ Enable debug mode (or setLTTNG_ANALYSES_DEBUGenvironment variable). yes bestie there's an env var, go off π--no-colorβ Disable colored output. (sad, but sometimes you need plain text, we get it)--no-progressβ Don't display the progress bar--min MINβ Filter out durations shorter thanminusec--max MAXβ Filter out durations longer thanmaxusec--logβ Output the I/O requests in chronological order. chronological order?? she's so organized β¨--limit LIMITβ Limit to top X (default =10)--topβ Output the top I/O latencies by category--statsβ Output the I/O latency statistics--freqβ Output the I/O latency frequency distribution--freq-resolution FREQ_RESOLUTIONβ Frequency distribution resolution (default20)--freq-uniformβ Use a uniform resolution across distributions--freq-seriesβ Consolidate frequency distribution histogram as a single one--usageβ Output the I/O usage--minsize MINSIZEβ Filter out, I/O operations working with less thatminsizebytes--maxsize MAXSIZEβ Filter out, I/O operations working with more thatmaxsizebytes
π«Ά quick reminder bestie:--period-endliterally will not work without--period-begin. don't come crying to me, come crying to the manpage, because it said it first.
and that's the whole page!! every single flag, argument, default, env var and path accounted for, nothing skipped, nothing invented, fr fr. π
this was LTTng Analyses v0.6.0, dated January 2017 β a whole legend from the LTTng Analyses era, still out here doing IO latency top things. mwah. π π π¦ β π
π¦ where this page comes from
- debian bookworm: python3-lttnganalyses 0.6.1-3 Β· MIT
- ubuntu jammy: python3-lttnganalyses 0.6.1-2 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms