New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 672971 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Make x-axis linear in perf-dashborad graphs

Project Member Reported by majidvp@chromium.org, Dec 9 2016

Issue description

The x-axis in the graph is not linear which can be misleading. 

For example see: https://chromeperf.appspot.com/group_report?bug_id=540824
Screenshot with more info here: https://screenshot.googleplex.com/oCVaoLQ7c3t.png


Because the x-axis is not linear it is very difficult to notice that the range in which the regression occurred is very large. This large range would have raised a red flag when deciding to investigate the issue but it was missed leading to many failed bisects. 



 
Cc: eakuefner@chromium.org jessimb@chromium.org
Ethan, Jessi, is this already tracked in catapult?

We do plan to make the x-axis linear to chromium commit positions (which would make it hard to see when a large v8 roll is going in, for example, but probably be more intuitive to most chromium developers)
Linear to chromium commit positions sgtm.
It is not specifically tracked yet; there are comments here and there about the need (https://github.com/catapult-project/catapult/issues/2940). Should I create a catapult bug for it?
Yes, please, and archive this one with a link to the catapult one.
Status: Archived (was: Untriaged)
This bug is being tracked here
https://github.com/catapult-project/catapult/issues/3086
Components: Speed>Dashboard
Labels: -Performance-Dashboard

Sign in to add a comment