Make the Y-axis range match for keys across runs

[janaknat]

This helps to make it easy to compare the graphs without the need to adjust the y-axis range manually.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

kernel-build.tar.gz

[wash-amzn]

In the provided report, the left-side menu isn't staying pinned, but that change was already merged ...

[wash-amzn]

Now we need to get matched graphs aligned horizonally.

And default to hiding the pairs of graphs when they are all-zeros.

[janaknat]

Now we need to get matched graphs aligned horizonally.

And default to hiding the pairs of graphs when they are all-zeros.

That is the next PR. The graph will be empty with no points if that key did not exist for a particular run.

[janaknat]

In the provided report, the left-side menu isn't staying pinned, but that change was already merged ...

That PR got merged after this branch was made.

[wash-amzn]

Some of these new structs got named starting with End and others did not.

If you're going to continue making changes across all data types, at least try and keep the naming consistent.

[janaknat]

Yeah. Used End for all the structs.

[wash-amzn]

How does an initial value of high get set?

Does this only work because something like value > undefined always winds up being true?

If there's only a single data-point, does high remaining undefined crash the report?

[janaknat]

The data structure is initialized with 0 for low and high. After that, when update_limits is called the low and high are set.

[wash-amzn]

So you're crossing your fingers here that we never have a negative value?

Set both to the first value.

[janaknat]

We technically don't support negative numbers. When we do get it, we cast it to uint and use that. See GraphLimitType which has 3 variants, uint64, int64 and f64. int64 casts the value to u64 and re-uses uint64's implementation.