con / duct

A helper to run a command, capture stdout/stderr and details about running
MIT License
1 stars 1 forks source link

Summarize total resource consumption over all PIDs #39

Closed asmacdo closed 3 weeks ago

asmacdo commented 4 weeks ago

Since gathering maxes for each sample and then totaling at report generation time will overestimate usage, instead we will collect "totals" for each sample, but only report the spikes.

yarikoptic commented 3 weeks ago

I think it would be useful to have "average cpu%" probably more than "max cpu%" (spike) since that one I think most of them time would be some 100%. Average is a sum/number_of so you can keep adding and also keep track (increment number) on how many times you added to come up with a mean. The same could be done for memory (although there average is less useful but still might be)

asmacdo commented 3 weeks ago

Added a separate issue for averages