LTTNG-SCHEDFREQ(1)

✨ NAME ✨

lttng-schedfreq — LTTng analyses Scheduler frequency 💅

(that's the manual page lttng-schedfreq(1), bestie, section 1, User Commands — we're doing this 🫶)

🌸 DESCRIPTION 🌸

okay so. here's the whole vibe of what you type:

usage: lttng-schedfreq [-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>

The sched command. that's it, that's the whole energy. 🔥

🎀 positional arguments

• <path/to/trace> — the trace path, babe. point it at ur trace and let her cook ✨

💖 optional arguments

• -h, --help — show this help message and exit 🫶 (the classic "what do I even type" button)
• -r REFRESH, --refresh REFRESH — Refresh period, with optional units suffix (default units: s) ⏱️
• --gmt — Manipulate timestamps based on GMT instead of local time 🌍
• --skip-validation — Skip the trace validation 🙈 (living dangerously, we love that for u)
• --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) 🐛
• --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 ✂️
• --procname PROCNAME — Filter the results only for this list of process names 🏷️
• --tid TID — Filter the results only for this list of TIDs 🏷️
• --freq — Output the frequency distribution of sched switch latencies 📈
• --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 latencies 🥇
• --log — Output the sched switches in chronological order 📜
• --stats — Output sched switch statistics 🧮
• --total — Group all results (applies to stats and freq) 🫂
• --per-tid — Group results per-TID (applies to stats and freq) (default) 🧵
• --per-prio — Group results per-prio (applies to stats and freq) 🎚️

ok bestie real talk: --period-end needs --period-begin to come along, and --period-end-key will just borrow --period-begin-key if u don't hand it one. that's not me being extra, that's literally what the page says 💀

and that's the whole page, periodt 💅

this lil love letter came to u from LTTng Analyses v0.6.0, dated January 2017 — and yeah, LTTNG-SCHEDFREQ(1) is the header at the top, LTTng Analyses v0.6.0 January 2017 LTTNG-SCHEDFREQ(1) is the footer at the bottom, and u just read the middle. iconic. go analyze some sched switches, bestie 🦋✨💖