Those numbers look wrong somehow.
To compare, I have 8 days uptime and pulled these numbers:
# ps auxw | grep systemd
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 383 0.0 0.1 64132 29144 ? Ss Jun17 0:26 /lib/systemd/systemd-journald
root 443 0.0 0.0 45820 5128 ? Ss Jun17 0:01 /lib/systemd/systemd-udevd
message+ 1143 0.0 0.0 44596 5648 ? Ss Jun17 7:33 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root 1221 0.0 0.0 28596 3032 ? Ss Jun17 0:01 /lib/systemd/systemd-logind
root 1256 0.0 0.0 29880 1596 ? Ss Jun17 0:00 /sbin/cgmanager -m name=systemd
maow 2435 0.0 0.0 45500 4952 ? Ss Jun17 0:00 /lib/systemd/systemd --user
I've shown my uptime and same command you ran (I did manually put column headers on there for clarity) and they're not even in the same ballpark.
I'm reminded of the old joke, "Windows is a bloated resource hog - look, System Idle Process is using up all my resources!"
Anyway, would be interesting to see what others post.
And now I add filler due to Filter error: Please use fewer 'junk' characters. message I get from Slashdot while trying to post this.
Oh Slashdot, I keep upping the regular text to copied / pasted text ratio and you keep giving me Filter error.
I removed the output line from "ps" so the grep command itself didn't show. Now can I preview this?
Now I've removed the uptime output, can I please preview this?
FOR FUCK SAKE. After removing & adding back lines of ps output, I had to drop one line.
And, after several previews & edits, I can now put the line back and /. doesn't complain. WTF?