Shortcut for live plot of memory usage?

[gamesbook]

Shortcut for live plot of memory usage?

[tenox7]

thank you, I will update the doc; in general however the examples are not meant to be exhaustive or even fully correct on all systems, just a general samples of how the app can be used

[hartwork]

@tenox7 unless I'm overlooking something, it would be worth labelling examples that should not be run verbatim, because many of them do work well with copy-pasting and it doesn't seem unreasonable to then expect that approach to work well with other examples also. So if some examples are more like templates that need adjustment, let's make sure that's impossible to not notice before first running the command.
I theory we could also turn most of these samples into files named like ttyplot-ram-usage or so on and maintain them and enrich them with checks for command availability and such, but we may get flooded with pull requests then, I don't know 😄

[tenox7]

I like the idea of have scripts with concrete metrics. We could write shell scripts that not only check command availability but also resolve OS differences between Linux/BSD/MacOS, etc. I have a bunch of scripts myself that I wanted to add but they are little beyond what I want in examples. I'm ok with getting flood of pull requests for these. What I'm unclear is how to actually distribute them. Should it go to the package? if so where should they land? Maybe have one shell script that takes argument of a metric?

In respect of examples in the readme I have a feeling that there already is too many of them, and definitely too many are using awk. I want to convert more to sed/perl, maybe python? Also there is too much sar, I think for memory usage I would like to use free perhaps? These are supposed to be just examples and not exhaustive.

[hartwork]

I like the idea of have scripts with concrete metrics. We could write shell scripts that not only check command availability but also resolve OS differences between Linux/BSD/MacOS, etc. I have a bunch of scripts myself that I wanted to add but they are little beyond what I want in examples.

@tenox7 I see!

I'm ok with getting flood of pull requests for these.

A flood of pull requests will need quick response times to not end up in frustration.

What I'm unclear is how to actually distribute them. Should it go to the package?

Probably yes, they would become part of the API then though meaning that usage of a script cannot just change in breaking ways without a major version bump or frustrate users.

if so where should they land?

For candidates:

• /usr/bin if scripts are named ttyplot-<something>
• (/usr/sbin if only root should use them. Probably not.)
• /usr/lib/ttyplot/bin/ if we want to stay out of ${PATH} with lib or /usr/lib/ overridable by distros
• /usr/libexec/ttyplot/ if we want to stay out of ${PATH}

Needs checking against FHS, was only brainstorming so far.

Maybe have one shell script that takes argument of a metric?

I'm not sure that will give good maintainability. I'd prefer a bunch of independent scripts where each can be fixed without breaking the rest of them.

In respect of examples in the readme I have a feeling that there already is too many of them, and definitely too many are using awk.

Too many seems like a concern of discoverability and/or cognitive overload. Good organization would be an alternative to dropping existing useful bits.

I want to convert more to sed/perl, maybe python?

How would sed be better than awk?
Keeping Perl out of this would be my main concern, I'd be good with any of sed, awk, Python 3 and the more readable, the better (if still reasonably portable).

Also there is too much sar, I think for memory usage I would like to use free perhaps?

Maybe, I don't have sar installed and I need to know or research that I need package "sysstat" installed for it. Not a showstopper to me personally though.

These are supposed to be just examples and not exhaustive.

Understood, yes.

[edgar-bonet]

@hartwork suggested:

For candidates: • /usr/bin [...]

Rather /usr/local/{bin,lib,man...}. This is where non-distro stuff is typically installed. And it should be easy to override by distro packagers, who would move that to /usr/{bin,lib,man...}.

[hartwork]

@edgar-bonet $(PREFIX)/bin, you're right 👍