LTTNG-PERIODTOP(1)

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

πŸ’… NAME πŸ’…

lttng-periodtop β€” LTTng analyses period top, bestie. It's giving "let me show you the period tea" ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so, real talk: the usage is literally this, and I am NOT paraphrasing the flags, they're staying exactly as they are, periodt:

usage: lttng-periodtop [-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] [--freq]
       [--freq-resolution FREQ_RESOLUTION] [--freq-uniform]
       [--freq-series] [--limit LIMIT] [--top] [--log] [--stats]
       [--min-duration MIN_DURATION] [--max-duration MAX_DURATION]
       [--aggregate-by AGGREGATE_BY] [--select SELECT] [--group-by
       GROUP_BY] [--order-by ORDER_BY] <path/to/trace>

The periods command. that's it, that's the whole vibe check πŸ’–


🌸 positional arguments: 🌸

  • <path/to/trace> β€” the trace path, bestie. Point me at it πŸ‘‘

✨ optional arguments: ✨

  • -h, --help β€” show this help message and exit. classic, iconic, never misses 🫢
  • -r REFRESH, --refresh REFRESH β€” Refresh period, and you can slap an optional units suffix on it (default units: s).
  • --gmt β€” Manipulate timestamps based on GMT instead of local time. no more timezone drama πŸ•
  • --skip-validation β€” Skip the trace validation. living dangerously, love that for you πŸ’€
  • --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)
  • --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
  • --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
  • --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). bestie it's telling you the env var, use it πŸ›
  • --no-color β€” Disable colored output. tragic, but sometimes you're piping it somewhere, iykyk πŸ™ˆ
  • --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
  • --freq β€” Output statistics about periods durations
  • --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
  • --limit LIMIT β€” Limit to top X (default = 10)
  • --top β€” Output the top sched switch durations
  • --log β€” Output the sched switches in chronological order
  • --stats β€” Output sched switch statistics
  • --min-duration MIN_DURATION β€” Filter out, periods shorter that duration (usec)
  • --max-duration MAX_DURATION β€” Filter out, periods longer than duration (usec)
  • --aggregate-by AGGREGATE_BY β€” FIXME
  • --select SELECT β€” FIXME
  • --group-by GROUP_BY β€” Present the results grouped by a list of fields(period.captured_field[, period.captured_field2])
  • --order-by ORDER_BY β€” hierarchy, time

and that's the whole page, no notes πŸ’… This one's from LTTng Analyses v0.6.0, dated January 2017, and it's filed under LTTNG-PERIODTOP(1) β€” the man page name, in case you were wondering where it went, bestie πŸŽ€ mwah, go analyze some periods βœ¨πŸ‘‘

πŸ“¦ where this page comes from