LTTNG-MEMTOP-MI(1)

💖 lttng-memtop-mi 💖

okay bestie, so this is a User Commands page (section 1, for the record) for lttng-memtop-mi, and it is literally the machine interface for LTTng's memory top. Like, it does the memtop thing, but in a way that machines can chew on. no cap. 🫶

✨ NAME ✨

lttng-memtop-mi — LTTng analyses memory top machine interface 🌸

🎀 DESCRIPTION 🎀

bestie. here is the whole usage situation, verbatim, do not come for me:

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

The memtop command. that's the whole vibe. 💅

🌈 positional arguments:

• <path/to/trace> — the trace path. that's it, that's the one thing you gotta hand over. it's giving "where's the trace bestie" energy. 🔥

👑 optional arguments:

• -h, --help — show this help message and exit. classic. iconic. we love a help flag.
• -r REFRESH, --refresh REFRESH — Refresh period, with an optional units suffix (default units: s). so like, if you don't say a unit, it's seconds. noted. ⭐
• --gmt — Manipulate timestamps based on GMT instead of local time. GMT girlies rise up 🌍
• --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 (requires --period-begin). so if you try to use this one alone, nah, it needs its bestie 🫶
• --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. it just copies its friend's homework, honestly relatable 🎀
• --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. very demure, very mindful 💅
• --debug — Enable debug mode (or set LTTNG_ANALYSES_DEBUG environment variable). yes bestie, there IS an env var, go set it 🦋
• --no-color — Disable colored output. (but why would you 😭)
• --no-progress — Don't display the progress bar
• --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). ten. the default is ten. write it down 📝
• --top — Output the top results

ok so real talk: <path/to/trace> is the only positional thing, and every single one of those optional flags above is optional. no skipping, no merging, no "eh close enough" — they're all in there, exactly as written. 🧚

and that's the page, bestie!! this whole thing comes to you from LTTng Analyses v0.6.0, dated January 2017 — vintage but still serving ✨ periodt 💖🌸👑