Feature Request
More precise numbers in performance overview
Current Status:
Completed
kolizz
In Pulse, the Performance tab at the top. These numbers could use some more precision. Just showing "2s" median/avg/P90/P99 load time could mean a full second difference on just 2 seconds, a rather big difference. More than 10 s could maybe get less precision, but anything below should probably be in ms and even above it would be nice to keep at least one decimal point in seconds.
The reason for me wanting this is that I want to keep track of how these numbers change over time. No need for full reporting if I can just select a time period and get a precise enough number from this page :).
Raygun
John-Daniel Trask
Posted on
Nov 09 2016
Hi,
Great feedback - thank you!
We're presently undertaking a big overhaul of how we generate the numbers in Pulse, so I'll make sure the team are aware of this thread and incorporate it into that work they're doing.
If you don't mind, they may also reach out about getting you on early access to these changes once they're ready. Let me know if you'd be open to that.
Thank you,
John-Daniel Trask
Callum
Posted on
Nov 09 2016
Thanks for the great request, this was an excellent improvement to spot. As John-Daniel notes we're working on this area currently and I was able to get a hotfix applied just now. As a result when you next reload Pulse you'll see that the stats timing figures are displayed to 2DP. We hope this improves Pulse for you and you continue to find the product useful.
Regards,
Callum Gavin
Raygun Limited
kolizz
Posted on
Nov 10 2016
Thank you! That solved my use case. Looking forward to the bigger changes as well :).