Trace viewer precision

[danstarns]

• Time Epic #4

Problem

The trace viewer doesn't accurately display the whole trace, see in the screenshot how we are only plotting spans in MS and not accounting for those spans that are of a lesser value.

Due to the fact, we dont account for spans that are of a smaller value than an MS, the width and offset of each trace in the viewer is skewed.

[Tohaker]

Trying out a few things, got it displaying the right units at least, depending on how big the durationNano value is

Figuring out the width and making the logic reusable will be the next steps

[Tohaker]

Played around with some BigInt maths, the existing logic appears overly complicated since it was trying to contextualise everything into ms whereas all we needed was a percentage of the total time span. Resolution was also being lost when casting to Number so that's been saved for the last step of the calculations

[Tohaker]

Finally, some proper precision in calculating the time;

I've placed the logic from the Span component into the unix-nano module so it's all contained in one place, and got some janky BigInt maths holding it all together. I suppose as we're targeting developers machines, browser support isn't top priority and most of this stuff is supported by recent versions of all major browsers so users shouldn't have too hard a time running it