LTTNG-PERIODFREQ(1)
π LTTNG-PERIODFREQ π
okay bestie, welcome to the LTTng Analyses corner of the manual pages β this one's lttng-periodfreq, section 1 (User Commands), and she's here to analyse period frequency. no cap. let's get into it π¦
β¨ NAME β¨
lttng-periodfreq β LTTng analyses period frequency πΈ
π DESCRIPTION π
the usage, verbatim, because I would never gatekeep a synopsis:
usage: lttng-periodfreq [-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>
it's the periods command. that's the whole vibe. periodt. π
π positional arguments π
<path/to/trace>β the trace path, aka where your little trace files live π«Ά
π optional arguments π
-h,--helpβ shows this help message and dips. iconic.-r REFRESH,--refresh REFRESHβ refresh period, and yes you can slap a units suffix on it (default units:s) β±οΈ--gmtβ manipulates timestamps based on GMT instead of local time π--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 (and heads up, 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, a list of event field names used to match period marker. if none is specified, it just uses the same as--period-begin-key--period-key-value PERIOD_KEY_VALUEβ optional, define a fixed key value that a period must correspond to in order 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β shows the program's version number and exits--debugβ enable debug mode (or just set theLTTNG_ANALYSES_DEBUGenvironment variable, same energy) π--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--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 fr, that's literally what it says, I'm not making stuff up)--select SELECTβFIXMEπ (same, bestie)--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
no notes, just vibes: if something says FIXME, that's the manpage's words, not mine. I keep it π― real and I keep it exact.
that's the whole page, bestie β every flag, every default, every FIXME, all of it. nothing skipped, nothing invented. π§
this cutie is from LTTng Analyses v0.6.0, dated January 2017, and it lives in section 1 of the manual. take care of her, she's been holding it down since 2017 and she still ate πβ¨ππ¦πΈπ«Άππβπ
π¦ 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