LTTNG-IOLATENCYSTATS-MI(1)

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

πŸ’– NAME πŸ’–

lttng-iolatencystats-mi β€” bestie, this is the LTTng analyses IO latency statistics machine interface. It's the little tool that stares at your trace and tells you exactly how long your I/O was out here taking. no cap. πŸ‘‘


✨ DESCRIPTION ✨

okay so here's the whole vibe, the entire usage situation, copy-pasted with love (do NOT retype this, just look at it):

usage: lttng-iolatencystats-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 it, that's the whole thing, it's giving "I analyze I/O and I do it flawlessly" πŸ’…


πŸŽ€ positional arguments: πŸŽ€

  • <path/to/trace> β€” the trace path. literally just point her at the trace and she'll go. 🌸

πŸ¦‹ optional arguments: πŸ¦‹

  • -h, --help β€” show this help message and exit. classic. iconic. the moment you forget everything else exists. ✨
  • -r REFRESH, --refresh REFRESH β€” refresh period, with an optional units suffix (default units: s). so like, s for seconds unless you say otherwise, bestie. ⏱️
  • --gmt β€” manipulate timestamps based on GMT instead of local time. your timezone drama, but make it UTC. 🌍
  • --skip-validation β€” skip the trace validation. speedrun mode, no vibe check, we trust you fr fr πŸ™ˆ
  • --begin BEGIN β€” start time: hh:mm:ss[.nnnnnnnnn]
  • --end END β€” end time: hh:mm:ss[.nnnnnnnnn]
  • --period PERIOD β€” period definition. define your period, queen. 🩸
  • --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: this one requires --period-begin. they're a package deal, a duo, a friendship bracelet situation. 🫢
  • --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 none is specified, it uses the same --period-begin-key. sharing is caring. πŸ’ž
  • --period-key-value PERIOD_KEY_VALUE β€” optional, define a fixed key value to which a period must correspond to be considered. very "you must be this specific to get in" energy. 🎟️
  • --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 ✨ approximated ✨
  • --no-intersection β€” disable stream intersection mode. we're not doing the overlap thing today. 🚫
  • -V, --version β€” show program's version number and exit. hi, what version are you? πŸ’–
  • --debug β€” enable debug mode (or set the LTTNG_ANALYSES_DEBUG environment variable). turn the volume all the way up. πŸ”₯
  • --no-color β€” disable colored output. for when the rainbow is too much (rude, but okay). 🌈
  • --no-progress β€” don't display the progress bar. she's shy today. πŸ™ˆ
  • --min MIN β€” filter out durations shorter than min usec. tiny things, begone. ⭐
  • --max MAX β€” filter out durations longer than max usec. big things, also begone. πŸ’€
  • --log β€” output the I/O requests in chronological order. timeline moment, main character energy. πŸ“œ
  • --limit LIMIT β€” limit to top X (default = 10). only the top ten get to speak. πŸ’…
  • --top β€” output the top I/O latencies by category. the ranking, the leaderboard, the awards show. πŸ†
  • --stats β€” output the I/O latency statistics. the numbers. the lore. πŸ“Š
  • --freq β€” output the I/O latency frequency distribution. how often everything happens, lowkey fascinating. 🌸
  • --freq-resolution FREQ_RESOLUTION β€” frequency distribution resolution (default 20).
  • --freq-uniform β€” use a uniform resolution across distributions. consistency, we love her. πŸŽ€
  • --freq-series β€” consolidate frequency distribution histogram as a single one. one histogram to rule them all. πŸ‘‘
  • --usage β€” output the I/O usage. what's actually getting used, iykyk. πŸ¦‹
  • --minsize MINSIZE β€” filter out I/O operations working with less than minsize bytes. πŸ“
  • --maxsize MAXSIZE β€” filter out I/O operations working with more than maxsize bytes. 🌟

not me ending this with the receipts: this whole page is LTTng Analyses v0.6.0, dated January 2017, and it lives under the manual name LTTNG-IOLATENCYSTATS-MI(1). πŸ’œ

okay bestie that's the whole manual, go analyze some I/O, you're literally going to slay. periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from