LTTNG-IOLATENCYTOP(1)

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

πŸ’… 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 set LTTNG_ANALYSES_DEBUG environment 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 than min usec
  • --max MAX β€” Filter out durations longer than max usec
  • --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 (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
🫢 quick reminder bestie: --period-end literally 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