Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wild variances in v3 #65

Closed
Snugug opened this issue Aug 7, 2020 · 3 comments
Closed

Wild variances in v3 #65

Snugug opened this issue Aug 7, 2020 · 3 comments

Comments

@Snugug
Copy link

Snugug commented Aug 7, 2020

I'm using v3, running a live url 3 times. The URLs are all hitting Firebase's hosting CDN, so they're very stable performance-wise. In my latest run, my Performance score across 3 runs was 24, 73, 73. The exact same site, with identical code, run from the same infra, but at a different URL is reporting values of 89, 74, and 72. When running Lighthouse from Chrome, the same URLs consistently have a performance score of between 85-87. I'm curious as to why there is so much variance in the actions version of Lighthouse as compared to the browser version, and if there's any way to stabilize the results.

Thanks!

@exterkamp
Copy link
Collaborator

Do you have the benchmark indices of those variant runs? Or know the time the github-action took to run?

I know in the past sometimes github had bad days and actions VMs were really flaky. #14

@alekseykulikov
Copy link
Member

Yes, would be interesting to see benchmarkIndex values. They should be around 750 to be trustable.
We need to enable PSI as an alternative runner GoogleChrome/lighthouse-ci#251

@alekseykulikov
Copy link
Member

Let's keep the track of variance in #14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants