LTTNG-MEMTOP(1)

πŸ“¦ version 0.6.1, in debian bookworm, ubuntu jammy

πŸ’– LTTNG-MEMTOP β€” lttng-memtop πŸ’–

okay bestie, welcome to the LTTng analyses memory top page, from the LTTNG-MEMTOP(1) manual (User Commands section, obvi). it lives in the LTTng Analyses universe and it's here to show you who's eating all the memory. no cap. 🫢


✨ NAME ✨

lttng-memtop β€” LTTng analyses memory top. that's it, that's the vibe. she analyzes, she tops, she serves memory stats. πŸ‘‘


🌸 DESCRIPTION 🌸

here's how you summon her, fr fr:

usage: lttng-memtop [-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>

lowkey that's a lot of flags but we're gonna go through every single one together, hand in hand. 🫢

ngl, the description in the original is literally just "The memtop command." so. there it is. the memtop command. iconic behaviour honestly. πŸ’…

πŸŽ€ positional arguments πŸŽ€

  • <path/to/trace> β€” the trace path. this is literally where your trace lives. you gotta give her this or she has nothing to look at. πŸ’–

πŸ¦‹ optional arguments πŸ¦‹

  • -h, --help β€” shows this help message and exits. the classic. the "help me i'm lost" button. πŸ™ˆ
  • -r REFRESH, --refresh REFRESH β€” the refresh period, and you can slap an optional units suffix on it (default units: s). so like, she'll re-draw the screen on that rhythm. ⭐
  • --gmt β€” manipulate timestamps based on GMT instead of local time. timezone girlie behaviour. 🌈
  • --skip-validation β€” skip the trace validation. yolo mode, essentially. πŸ”₯
  • --begin BEGIN β€” start time, formatted like hh:mm:ss[.nnnnnnnnn]. yes, nanoseconds are invited to the party. ✨
  • --end END β€” end time, formatted like hh:mm:ss[.nnnnnnnnn]. same deal, other end of the window. πŸ’œ
  • --period PERIOD β€” period definition. she likes a defined period, periodt. πŸŽ€
  • --period-captures PERIOD_CAPTURES β€” period captures definition.
  • --period-begin PERIOD_BEGIN β€” analysis period start marker event name. this is the event that screams "PERIOD STARTS NOW". πŸ“£
  • --period-end PERIOD_END β€” analysis period end marker event name. ⚠️ requires --period-begin, so don't come in with an end and no beginning, bestie, that's not how arcs work.
  • --period-begin-key PERIOD_BEGIN_KEY β€” optional, a list of event field names used to match period markers (default: cpu_id). so if you don't say anything, it's riding with cpu_id. πŸ’…
  • --period-end-key PERIOD_END_KEY β€” optional, a list of event field names used to match the period marker. if none are specified, it uses the same as --period-begin-key. matching outfits, cute. πŸŽ€
  • --period-key-value PERIOD_KEY_VALUE β€” optional, defines a fixed key value that a period must correspond to in order to be considered. like a lil bouncer at the door. πŸ‘‘
  • --cpu CPU β€” filter the results only for this list of CPU IDs. pick your fave CPUs. πŸ–₯️
  • --timerange TIMERANGE β€” time range, written as [begin,end]. brackets stay on. 🌸
  • --progress-use-size β€” use trace size to approximate progress. approximation girlie. ✨
  • --no-intersection β€” disable stream intersection mode. she's turning off the overlap-matching, okay?? 😭
  • -V, --version β€” show the program's version number and exit. quick lil flex. πŸ’…
  • --debug β€” enable debug mode (or set the LTTNG_ANALYSES_DEBUG environment variable). yes she does accept env vars, she's flexible like that. 🧚
  • --no-color β€” disable colored output. for when you're feeling monochrome and minimal (we support you but we don't get it). πŸ’€
  • --no-progress β€” don't display the progress bar. no lil bar creeping across your terminal, you're on your own. πŸ“
  • --procname PROCNAME β€” filter the results only for this list of process names. name names, bestie. πŸ”
  • --tid TID β€” filter the results only for this list of TIDs. thread IDs only, we're being specific. 🧡
  • --limit LIMIT β€” limit to top X (default = 10). so by default you get the top ten, and you can change that number to whatever your heart desires. πŸ’–
  • --top β€” output the top results. this is literally the whole point of a memtop, but go off. πŸ‘‘

πŸ’œ SEE ALSO πŸ’œ

no SEE ALSO section in this one bestie β€” the original doesn't have one, so we're not inventing references. keeping it honest, fr fr. 🫢


that's the whole page!! every flag, every default, every format string, all present and accounted for, nothing skipped, no cap. πŸ¦‹

LTTng Analyses v0.6.0 β€” January 2017 πŸŽ€

and that's the sign-off from your favourite LTTNG-MEMTOP(1) manual, written with love, hype, and absolutely zero removed options. go analyze that memory, main character. βœ¨πŸ‘‘πŸ’–

πŸ“¦ where this page comes from