(In reply to Dave Hunt [:davehunt] [he/him] ⌚BST from comment #5)
We should extend this to all views, so once we have the unit data we can include it in graph, compare, alerts, etc.
igoldan: As this involves the graphs view, do you think we could include this in our Q4 work?
Yes, we can include this into Q4.
What's involved here? I imagine we could add a 'unit' field in the schema, which could be bytes, seconds, etc. Tests would then need to provide this information, allowing us to format the display of the results accordingly (defaulting to the current behaviour).
I believe this is the indeed the way to proceed. Some of the tests already provide a measurement unit (the schema allows this).
After updating the schema, we'll need to add measurement units to those that don't. Likely, we'll sync with some of the test owners.
The tricky part will be Perfherder's ingestion pipeline. We need to make it aware of measurement units. At this moment, I'm not sure whether this new field should be part of a perf signature. Basically, what I'm asking is: if someone updates the measurement unit for a test, should we treat that as a whole new set of data?
After we address this problem, what'll be left are the actual UI displays of this unit.