LTTNG-IOUSAGETOP(1)
π LTTNG-IOUSAGETOP π
okay bestie, gather round, because this one is lttng-iousagetop from the LTTng analyses fam β it's the tool that does the whole "top" thing but for I/O. Yes. Like top, but for your I/O requests. She's a User Command, she's iconic, she's gonna tell you who's hogging the I/O. π¦
β¨ NAME β¨
lttng-iousagetop β LTTng analyses IO usage top
πΈ DESCRIPTION πΈ
ok so here's the vibe, the invocation goes a little something like this:
usage: lttng-iousagetop [-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>
The I/O command. π«Ά That's literally what it says. She's the I/O one.
π positional arguments π
<path/to/trace>β trace path. that's it, that's the whole thing. hand her the path to your trace and she'll do her little analysis thing. π
π optional arguments π
-h,--helpβ show this help message and exit. the classic. when in doubt,-hit out. β¨-r REFRESH,--refresh REFRESHβ Refresh period, with optional units suffix (default units:s). so you can say like5and it's 5 seconds, or give it a suffix if you're feeling fancy.--gmtβ Manipulate timestamps based on GMT instead of local time. no more "wait what timezone was this in" π--skip-validationβ Skip the trace validation. living dangerously, love that for you.--begin BEGINβ start time:hh:mm:ss[.nnnnnnnnn]. nanoseconds optional, diva behavior optional but encouraged.--end ENDβ end time:hh:mm:ss[.nnnnnnnnn]. same format, other end of the sandwich.--period PERIODβ Period definition. yes that's the whole description. slay.--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). β οΈ bestie she NEEDS her--period-begin, they're a package deal, don't separate them.--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 shares, it's cute.--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 faves.--timerange TIMERANGEβ time range:[begin,end].--progress-use-sizeβ use trace size to approximate progress. progress bar but make it estimated π--no-intersectionβ disable stream intersection mode. turning off the default, noted.-V,--versionβ show program's version number and exit.--debugβ Enable debug mode (or setLTTNG_ANALYSES_DEBUGenvironment variable). two ways to get the tea, your choice π--no-colorβ Disable colored output. for when the rainbow is too much (never, but okay).--no-progressβ Don't display the progress bar. she'll just sit there quietly, mysterious, main character energy.--min MINβ Filter out durations shorter thanminusec. bye tiny durations π--max MAXβ Filter out durations longer thanmaxusec. bye big durations π--logβ Output the I/O requests in chronological order. timeline girlies rise up.--limit LIMITβ Limit to top X (default =10). ten is the default. ten little faves.--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. (that's the original wording bestie, "less that", I'm just the messenger π«Ά)--maxsize MAXSIZEβ Filter out, I/O operations working with more thatmaxsizebytes. (again, "more that", verbatim, no cap)
π quick vibe check:--period-endwill NOT work without--period-begin. don't do it. don't be that girl.
that's the whole page babes, every flag accounted for, nothing skipped, we ate and left no crumbs. πβ¨
LTTng Analyses v0.6.0 π January 2017 β yeah she's an elder but she still serves. 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