LTTNG-IOLATENCYFREQ-MI(1)
π lttng-iolatencyfreq-mi β the manual, but make it a group chat π
okay bestie so this is lttng-iolatencyfreq-mi, aka the LTTng analyses IO latency frequency machine interface. say that five times fast, I dare you. it's the little command that looks at your trace and tells you how your I/O latencies are actually behaving. slay. β¨
πΈ NAME πΈ
lttng-iolatencyfreq-mi β LTTng analyses IO latency frequency machine interface. yes bestie, that's the whole name, it's giving "I couldn't decide which word to drop so I kept them all" and honestly? iconic. π
π¦ DESCRIPTION π¦
so here's how you call it, no cap:
usage: lttng-iolatencyfreq-mi [-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 the original says and I refuse to elaborate further. π
π positional arguments π
like, the one thing you have to give it:
<path/to/trace>β the trace path. hand it over. it's not optional bestie, it's the whole point. π«Ά
β¨ optional arguments β¨
okay this is the long part, grab a snack, hydrate, we're going in. π
-h,--helpβ show this help message and exit. the classic. the comfort option. whenever you're lost, she's there. π-r REFRESH,--refresh REFRESHβ refresh period, with an optional units suffix (default units:s). so if you just say5it means5s, got it? β±οΈ--gmtβ manipulate timestamps based on GMT instead of local time. GMT girlies rise up. π--skip-validationβ skip the trace validation. living dangerously, love that for you. π--begin BEGINβ start time, formatted likehh:mm:ss[.nnnnnnnnn]. the.nnnnnnnnnis nanosecond-level detail, because we're precise in this house. β--end ENDβ end time, same format:hh:mm:ss[.nnnnnnnnn]. β--period PERIODβ period definition. define your period. πΈ--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. heads up bestie: this one requires--period-begin. you can't end a period you never began, that's just math. π--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, it uses the same--period-begin-key. symmetrical queen. π--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, written as[begin,end]. brackets and all, don't @ me. β³--progress-use-sizeβ use trace size to approximate progress. big trace energy. π--no-intersectionβ disable stream intersection mode. π΄-V,--versionβ show program's version number and exit. the "who even am I" option. π--debugβ enable debug mode (or set theLTTNG_ANALYSES_DEBUGenvironment variable). yes, you can do it with a flag or an env var, choose your fighter. π--no-colorβ disable colored output. for when your terminal is in its minimalist era. π--no-progressβ don't display the progress bar. some of us just want peace. ποΈ--min MINβ filter out durations shorter thanminusec. little ones, begone. π--max MAXβ filter out durations longer thanmaxusec. big ones, also begone. π--logβ output the I/O requests in chronological order. time-ordered, as the universe intended. π--limit LIMITβ limit to top X (default =10). ten. that's the default. don't forget it. π--topβ output the top I/O latencies by category. the leaderboard, basically. π--statsβ output the I/O latency statistics. numbers girlies, this one's for you. π--freqβ output the I/O latency frequency distribution. the main character of this whole program, honestly. π--freq-resolution FREQ_RESOLUTIONβ frequency distribution resolution (default20). π--freq-uniformβ use a uniform resolution across distributions. consistent. reliable. π§--freq-seriesβ consolidate frequency distribution histogram as a single one. one histogram to rule them all. π₯--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. π§΅
π«Ά real talk bestie: that--period-endone needs--period-beginor it's not happening. that's the only gotcha here and I'm telling you up front so you don't text me at 2am. π
π SEE ALSO π
...okay so there's genuinely nothing listed here in the original, which is giving "I'm an only child." no cross-references, no siblings. just vibes. π¦
and that's the whole page, bestie!! you ate. periodt. π β¨
this was LTTng Analyses v0.6.0, dated January 2017 β yeah she's a vintage icon, a classic, timeless. ππ
π¦ 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