Right now we under pressure because of increasing memory consumption in dsvm jobs. So it'll be good to see which process is eating the most ram at a given time. It may not end up being useful, but it doesn't hurt to at least display just in case. Change-Id: I096bf4b425db51358240335e41f6238d1ec1bb40
1023 B
Executable File
1023 B
Executable File