Allow evaluating scaling performance on real-world data

[jonnor]

For a particular config, the scaling info (GuvScaled) and end-to-end job info - it should be possible to see how we actually did. That is, how often, and under what conditions, did jobs miss their deadline.

Somewhat related to #43

[jonnor]

Being able to extract the input rates is interesting for #43 - so we can see if changing max config would/may have solved a scenario, or if bringing it down would have caused problems in the past.
This may realistically require #96