To stop GC completely, debug.SetGCPercentage needs to receive a negative
integer. Passing a negative integer is cumbersome:
$ gops setgc <pid> -- -1
This commit adds a more user-friendly way to achieve that:
$ gops setgc <pid> off
This behavior is aligned with that of the GOGC env variable, where
negative or "off" can be set to stop the GC.
CircleCI tests currently seem fail consistently. GitHub actions
introduced in #136 are providing the same coverage (and more), have been
running stable for over a year and are easier to maintain. Thus, remove
Circle CI integration.
Ref. https://github.com/google/gops/pull/136#issuecomment-786529797
The current implementation assumes the given duration in seconds.
Instead, also allow to specify a duration in the format as expected by
`time.ParseDuration` and use that if found. If a plain integer is
specified, it is still parsed as a duration in seconds.
Commit 78435f89 changed the existing output format for the CPU usage
from `cpu usage:` to `cpu usage (all):`.
This might break existing scripts relying on this format. Revert that
part of the change and only report the CPU usage for the given period
with a suffix:
cpu usage: 0.087%
cpu usage (1s): 1.42%
Implemented a command, where users can list all running Go
processes in a tree-like format (like pstree).
Example:
$ gops tree
...
├── 13744
│ └── 71746 (gops) {go1.10}
├── 1
│ └── 13962 (gocode) {go1.9}
└── 557
└── 635 (com.docker.supervisor) {go1.9.2}
└── 638 (com.docker.driver.amd64-linux) {go1.9.2}
* update README snippets to reflect the new output
Updated the sample output in the README to match the
properly tabulated output when actually running the program.
