X-Axis Disagreement

[mgaudet]

Visit https://arewefastyet.com/win10/tp6-amazon?numDays=36, and scroll down
Notice that the X axes don't seem to agree:

[armenzg]

Hi @mgaudet I completely missed this. My apologies.

This has to do with how much data Perfherder has for a specific test. On that screenshot the ttfi did not have data before February.

If it helps visually we could investigate making the X-axis always start at the same place for all the graphs regardless if there's data. I'm leaning toward not fixing, however, I'm happy to mentor any interested contributor.

If we go to Perfherder for dcf and fcp we can tell that the AWFY graphs X-axis match with Perfherder:
https://treeherder.mozilla.org/perf.html#/graphs?timerange=31536000&series=mozilla-central,1870468,1,10
https://treeherder.mozilla.org/perf.html#/graphs?timerange=31536000&series=mozilla-central,1870464,1,10

[divyanshu-rawat]

@armenzg 👋 what this is about is it open to work on ?

[armenzg]

Hi!
I would honestly close this.

This is only noticeable when a new benchmark is added and there's less than 60 days worth of data (the default timerange).

If you load a full year you can notice it for some benchmarks. One of them starts from January while the other one starts from July (see screenshot).

[divyanshu-rawat]

@armenzg cool, so what is the proposed solution from youe end?

[armenzg]

Closing the issue.

Issue #195 is the next available issue.