Arvados

Rather than create separate feature requests for the same thing, I thought it would be better to consolidate them into one issue: [correct me if this is not the right procedure].

- A checklist of what you want to see on the graph.
If you want to watch only one task, someone should be able to check off task 1 to view.
If you want to view only the memory or only the memory usage, there should be a checklist for that too.

- Scrolling back in time
Maybe I would like to backtrack and see what happened before.

- Comments
I'm not sure if the points with 0 are useful (eth, blkio) [Maybe its my ignorance of what the graph is actually trying to convey]. It seems to take away from whats going on with what is going on with the numbers that are fluctuating. It would be nice to more focus on data that is moving than what is stagnant at 0.

I remember at the sprint review that the y-axis is hard to implement, but a thought could be using the max amount of memory/cache/swap available in the core as a benchmark? I would like to see if I'm using the max amount of RAM, so that I don't turn to swap for memory (because its so slow).