LTTNG-CPUTOP(1)

📦 version 0.6.1, in debian bookworm, ubuntu jammy

💻 lttng-cputop — bestie's guide to LTTng analyses CPU top ✨

okay so this is lttng-cputop from the LTTng Analyses manual (section 1, user commands, iykyk 💅) and it is literally the CPU-top analysis girlie of the LTTng universe. she looks at your trace and tells you which CPUs are doing the most. main character energy fr fr 👑

🌸 NAME 🌸

lttng-cputop — LTTng analyses CPU top

like. that's her. that's the whole vibe. she analyses CPU top. no cap 🎀

✨ SYNOPSIS ✨

usage: lttng-cputop [-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] [--procname PROCNAME] [--tid TID]
       [--limit LIMIT] [--top] <path/to/trace>

💖 DESCRIPTION 💖

The cputop command. that's it, that's the sentence. she's a cputop command and she knows it 🫶

🦋 positional arguments 🦋

  • <path/to/trace> — the trace path bestie. hand her your trace and she'll do her thing 🍓

🎀 optional arguments 🎀

  • -h, --help — shows this help message and dips. classic. show this help message and exit ✨
  • -r REFRESH, --refresh REFRESH — Refresh period, and you can slap an optional units suffix on it (default units: s, so seconds unless you say otherwise) ⏱️
  • --gmt — Manipulate timestamps based on GMT instead of local time. timezone relocation, slay 🌍
  • --skip-validation — Skip the trace validation. she's trusting you on this one, don't make it weird 🙈
  • --begin BEGIN — start time: hh:mm:ss[.nnnnnnnnn] — yes the nanoseconds are optional, she's flexible 💜
  • --end END — end time: hh:mm:ss[.nnnnnnnnn] — same deal, same format 🌸
  • --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, so don't be out here ending things you never started, that's not the vibe) 🏁
  • --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. she reuses, she recycles, she's eco-friendly 🌈
  • --period-key-value PERIOD_KEY_VALUE — Optional, define a fixed key value to which a period must correspond to be considered. picky in a cute way 💅
  • --cpu CPU — Filter the results only for this list of CPU IDs 🖥️
  • --timerange TIMERANGE — time range: [begin,end] — brackets included, she's specific like that ⭐
  • --progress-use-size — use trace size to approximate progress 📏
  • --no-intersection — disable stream intersection mode. streams stay in their own lanes, periodt 🛣️
  • -V, --version — show program's version number and exit. she'll tell you who she is 👑
  • --debug — Enable debug mode (or set the LTTNG_ANALYSES_DEBUG environment variable, your choice bestie, both routes work) 🐛
  • --no-color — Disable colored output. greyscale era, we respect it 🖤
  • --no-progress — Don't display the progress bar. no little bar, just vibes 😌
  • --procname PROCNAME — Filter the results only for this list of process names 🏷️
  • --tid TID — Filter the results only for this list of TIDs 🆔
  • --limit LIMIT — Limit to top X (default = 10) 🔟
  • --top — Output the top results 🥇
heads up bestie: --period-end genuinely will not work without --period-begin. that's a real dependency, not a suggestion 💀
also --period-end-key quietly borrows --period-begin-key if you leave it empty. it's giving "sharing is caring" 🫶

👑 SEE ALSO 👑

ngl there's nothing else listed here, she's a standalone queen. go run -h if you want the recap ✨

LTTng Analyses v0.6.0 🦋 January 2017 — okay that's the whole page, thank you for coming to my TED talk, go top some CPUs, love u bye 💖✨🎀

📦 where this page comes from