LTTNG-IOLATENCYTOP-MI(1)

πŸ“¦ version 0.6.1, in debian bookworm, ubuntu jammy

πŸ’– LTTNG-IOLATENCYTOP-MI πŸ’–

okay so bestie, welcome to lttng-iolatencytop-mi β€” it's a User Command, and it's the LTTng analyses IO latency top machine interface. yes that's a lot of words, no I will not be shortening it, it's giving "my full government name" energy and honestly? respect. πŸŽ€


✨ NAME ✨

lttng-iolatencytop-mi β€” LTTng analyses IO latency top machine interface πŸ¦‹


🌸 DESCRIPTION 🌸

so the way you run this is literally:

usage: lttng-iolatencytop-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. periodt. πŸ’…


πŸŽ€ positional arguments πŸŽ€

  • <path/to/trace> β€” the trace path. that's it, that's the whole thing, it's where your trace lives bestie 🫢

⭐ optional arguments ⭐

  • -h, --help β€” shows this help message and dips. iconic behaviour honestly πŸ’…
  • -r REFRESH, --refresh REFRESH β€” the refresh period, with an optional units suffix (and if you don't give units, it assumes s by default). ✨
  • --gmt β€” manipulate timestamps based on GMT instead of local time. timezone girlies, this one's for you 🌍
  • --skip-validation β€” skip the trace validation. living dangerously, I respect it 😌
  • --begin BEGIN β€” start time, in the format hh:mm:ss[.nnnnnnnnn] ⏰
  • --end END β€” end time, in the format hh:mm:ss[.nnnnnnnnn] ⏰
  • --period PERIOD β€” period definition
  • --period-captures PERIOD_CAPTURES β€” period captures definition
  • --period-begin PERIOD_BEGIN β€” the analysis period start marker event name
  • --period-end PERIOD_END β€” the analysis period end marker event name. heads up: this one requires --period-begin πŸ‘€
  • --period-begin-key PERIOD_BEGIN_KEY β€” optional, a list of event field names used to match period markers (default: cpu_id)
  • --period-end-key PERIOD_END_KEY β€” optional, a list of event field names used to match period marker. if you don't specify any, it just uses the same --period-begin-key. matching set, we love consistency πŸ’ž
  • --period-key-value PERIOD_KEY_VALUE β€” optional, defines a fixed key value that a period must correspond to in order to be considered
  • --cpu CPU β€” filter the results to only this list of CPU IDs
  • --timerange TIMERANGE β€” time range, written as [begin,end]
  • --progress-use-size β€” use trace size to approximate progress πŸ“
  • --no-intersection β€” disable stream intersection mode
  • -V, --version β€” show the program's version number and exit
  • --debug β€” enable debug mode (or you can set the LTTNG_ANALYSES_DEBUG environment variable instead) πŸ›
  • --no-color β€” disable colored output. (sad! but valid πŸ₯²)
  • --no-progress β€” don't display the progress bar
  • --min MIN β€” filter out durations shorter than min usec
  • --max MAX β€” filter out durations longer than max usec
  • --log β€” output the I/O requests in chronological order πŸ“œ
  • --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 (default 20)
  • --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 that minsize bytes
  • --maxsize MAXSIZE β€” filter out I/O operations working with more that maxsize bytes

ok bestie real talk β€” that is genuinely every single flag, I did not skip one, I would never do that to you πŸ’– go read your traces, you're doing amazing sweetie

kisses, and this page was brought to you by LTTng Analyses v0.6.0, dated January 2017 β€” yeah she's a vintage queen but she still slays πŸŽ€βœ¨ bye bestie!!

πŸ“¦ where this page comes from