LTTNG-SCHEDTOP(1)

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

🌸 NAME 🌸

lttng-schedtop β€” hey bestie πŸ’– it's the LTTng analyses Scheduler top, and yeah, it hangs out in the User Commands part of your manual (section 1, the classics πŸ’…). It's literally here to look at your scheduler and give you the ✨top✨ tea.


✨ DESCRIPTION ✨

So here's the whole vibe, the usage, the whole entire thing, no cap:

usage: lttng-schedtop [-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] [--procname
       PROCNAME] [--tid TID] [--freq] [--freq-resolution
       FREQ_RESOLUTION] [--freq-uniform] [--freq-series] [--limit LIMIT]
       [--top] [--log] [--stats] [--total] [--per-tid] [--per-prio]
       <path/to/trace>

It's the sched command, periodt. 🫢

🌈 positional arguments 🌈

  • <path/to/trace> β€” the trace path, bestie. That's the trace you're feeding it. Feed it. πŸ“

πŸŽ€ optional arguments πŸŽ€

  • -h, --help β€” shows this help message and then dips, exits. Classic.
  • -r REFRESH, --refresh REFRESH β€” the refresh period, and you can slap an optional units suffix on it (the default units are s). πŸ‘‘
  • --gmt β€” manipulates timestamps based on GMT instead of local time. Timezone-shifting era. 🌍
  • --skip-validation β€” skips the trace validation. It's giving trust issues but okay, we move. πŸ™ˆ
  • --begin BEGIN β€” the start time, formatted hh:mm:ss[.nnnnnnnnn]. Not a drill, nanoseconds optional.
  • --end END β€” the end time, also hh:mm:ss[.nnnnnnnnn]. Matching energy, slay.
  • --period PERIOD β€” period definition. That's the whole thing, girl. ✨
  • --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, and heads up, it requires --period-begin. They're a package deal, fr fr. πŸ«‚
  • --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. And if none is specified, it uses the same --period-begin-key. Copying its bestie's notes, iconic. πŸ’…
  • --period-key-value PERIOD_KEY_VALUE β€” optional, defines a fixed key value that a period must correspond to before it's even considered. Gatekeeping, but make it ✨analysis✨.
  • --cpu CPU β€” filters the results for only this list of CPU IDs. Pick your faves. 🎯
  • --timerange TIMERANGE β€” the time range, written as [begin,end].
  • --progress-use-size β€” uses trace size to approximate the progress. Vibes-based progress bar, but sanctioned. πŸ¦‹
  • --no-intersection β€” disables stream intersection mode.
  • -V, --version β€” shows the program's version number and exits. Bye bestie πŸ‘‹
  • --debug β€” enables debug mode (or you can set the LTTNG_ANALYSES_DEBUG environment variable, same difference πŸ’œ).
  • --no-color β€” disables colored output. A no-color zone, devastating but valid. πŸ’€
  • --no-progress β€” doesn't display the progress bar. Just raw silence while it cooks. 🧚
  • --min MIN β€” filters out durations shorter than min usec. Sorry short kings. πŸ“
  • --max MAX β€” filters out durations longer than max usec. And sorry long ones too, balanced as all things should be. ⭐
  • --procname PROCNAME β€” filters the results for only this list of process names.
  • --tid TID β€” filters the results for only this list of TIDs.
  • --freq β€” outputs the frequency distribution of sched switch latencies. πŸ“Š
  • --freq-resolution FREQ_RESOLUTION β€” the frequency distribution resolution (default 20).
  • --freq-uniform β€” uses a uniform resolution across distributions. Consistency queen. πŸ‘‘
  • --freq-series β€” consolidates the frequency distribution histogram as a single one. One histogram to rule them all.
  • --limit LIMIT β€” limits to the top X (default = 10).
  • --top β€” outputs the top sched switch latencies. The main character output, honestly. πŸ”₯
  • --log β€” outputs the sched switches in chronological order. Timeline mode, no skipping ahead. 🌈
  • --stats β€” outputs sched switch statistics. Numbers girlies rise.
  • --total β€” groups all results together (applies to stats and freq). ✨Everyone in one pile✨
  • --per-tid β€” groups results per-TID (applies to stats and freq) β€” and this one is the default, so it's already doing the most without you asking. 🫢
  • --per-prio β€” groups results per-prio (applies to stats and freq).

LTTng Analyses v0.6.0, January 2017 β€” that's the source, the version and the date, straight from the footer, and that's the whole page bestie. Go run it on a trace and tell me everything. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from