LTTNG-SCHEDLOG(1)
π NAME π
lttng-schedlog β LTTng analyses Scheduler log. bestie this is the sched one, the scheduler log reader, and she is thriving β¨
π¦ DESCRIPTION π¦
okay so real talk, here's how you call her:
lttng-schedlog [-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 the whole vibe, that's what she does π
π positional arguments π
<path/to/trace>β the trace path, aka where your data lives, bestie. point her at it and she'll do the rest π«Ά
β¨ optional arguments β¨
-h,--helpβ show this help message and exit. classic, iconic, never fails you π-r REFRESH,--refresh REFRESHβ Refresh period, with an optional units suffix (default units:s) β°--gmtβ Manipulate timestamps based on GMT instead of local time. timezone girlies rise π--skip-validationβ Skip the trace validation. living dangerously, we respect it π--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. heads up: this one requires--period-begin, she will not go alone π--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 theLTTNG_ANALYSES_DEBUGenvironment variable) π--no-colorβ Disable colored output. sad beige mode, no thank u π--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 (default20)--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)
ngl the flag list is long but she's just thorough, ok? not a red flag, it's a green one π
LTTng Analyses v0.6.0, January 2017 β mwah, love that for her, periodt πβ¨
π¦ where this page comes from
- debian bookworm: python3-lttnganalyses 0.6.1-3 Β· MIT
- ubuntu jammy: python3-lttnganalyses 0.6.1-2 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms