LTTNG-PERIODSTATS-MI(1)
β¨ NAME β¨
lttng-periodstats-mi β LTTng analyses period statistics machine interface π
πΈ DESCRIPTION πΈ
okay so bestie, this is the periods command, and it's giving machine interface energy. here's the whole vibe of how you call it:
usage: lttng-periodstats-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] [--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>
that's the whole shape of it, no cap. π
π«Ά POSITIONAL ARGUMENTS π«Ά
<path/to/trace>β the trace path, literally just point it at your trace and let her cook π¦
π OPTIONAL ARGUMENTS π
-h,--helpβ shows this help message and dips. classic. π-r REFRESH,--refresh REFRESHβ the refresh period, and you can tack a units suffix on it if you're feeling fancy (default units:s) β±οΈ--gmtβ manipulate timestamps based on GMT instead of local time π--skip-validationβ skip the trace validation. living dangerously, iconic π--begin BEGINβ start time, formatted likehh:mm:ss[.nnnnnnnnn]β--end ENDβ end time, same deal: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 (and heads up bestie, this one requires--period-begin) π--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, same thing but for the period end 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, but sometimes necessary) π«π--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 (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 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π (yes bestie, that's literally what it says, i'm not making it up)--select SELECTβFIXMEπ (same, we don't know either)--group-by GROUP_BYβ present the results grouped by a list of fields, written likeperiod.captured_field[, period.captured_field2]ποΈ--order-by ORDER_BYβ hierarchy, time β³
ngl,--aggregate-byand--selectare both markedFIXMEin the source. that's not me being shady, that's literally the documentation. use with vibes and caution π
and that's the whole page bestie!! π this was LTTng Analyses v0.6.0, dated January 2017, and the manual page is LTTNG-PERIODSTATS-MI(1). go forth and analyse those periods, you absolute main character ππβ¨
π¦ 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