-
Notifications
You must be signed in to change notification settings - Fork 886
docs: added benchmarks folder, benchmarks for v1.4.0 #2520
Conversation
# Identical (aside from PID) worker-binary lines removed | ||
worker-binary(24029): seconds alive: 18 avg CPU: 0.000000% avg Mem: 840 kB peak Mem: 840 kB | ||
worker-binary(23691): seconds alive: 19 avg CPU: 0.000000% avg Mem: 840 kB peak Mem: 840 kB | ||
rkt(23316): seconds alive: 23 avg CPU: 9.484321% avg Mem: 5 mB peak Mem: 20 mB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are there two rkt processes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No clue. I also can't seem to reproduce those results after rerunning this a handful of times. Here's output from when I ran it again, want me to swap the text in the PR with this?
derek@proton ~/go/src/github.com/coreos/rkt/tests/rkt-monitor> sudo ./rkt-monitor too-many-apps.podmanifest -d 30s
# Identical (aside from PID) worker-binary lines removed
rkt(17227): seconds alive: 20 avg CPU: 9.595387% avg Mem: 3 mB peak Mem: 20 mB
systemd(17253): seconds alive: 17 avg CPU: 0.329028% avg Mem: 16 mB peak Mem: 16 mB
systemd-journal(17255): seconds alive: 17 avg CPU: 0.000000% avg Mem: 6 mB peak Mem: 6 mB
worker-binary(17883): seconds alive: 17 avg CPU: 0.000000% avg Mem: 840 kB peak Mem: 840 kB
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Added the `Documentation/benchmarks` folder which includes a README that describes how rkt-monitor works and how to use it, and a file detailing the results of running rkt-monitor on each current workload with rkt v1.4.0.
Looks fine for now, we can iterate. |
Brazenly ignoring CI for this docs-only change. |
Added the
Documentation/benchmarks
folder which includes a README thatdescribes how rkt-monitor works and how to use it, and a file detailing
the results of running rkt-monitor on each current workload with rkt
v1.4.0.
Fixes #1788