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

document --shm-size and --cpus for consistent results #373

Merged
merged 1 commit into from
Jul 7, 2020

Conversation

iAmServerless
Copy link
Contributor

Related to GoogleChrome/lighthouse#9307

lighthouse fails to get results of heavy content pages if chrome has limited docker shared memory.
Using --shm-size=2g fixes this issue.

Another advice about using --cpus to control the CPU available to the lighthouse.

I also want to include advice to run a single test at a time on a dedicated machine to ensure equal CPU cycle availability between tests. This leads to the most consistent results but this seems infeasible in most cases. Scenarios like web.dev and page speed insight will have exponential hardware costs if they go this way. We are doing this at housing.com which has limited resource requirements. Please advice.

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @ashuanindian this is great! 🎉

@patrickhulce patrickhulce merged commit 6616a4a into GoogleChrome:master Jul 7, 2020
denkrasnov pushed a commit to Travix-International/lighthouse-ci that referenced this pull request Oct 29, 2020
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

Successfully merging this pull request may close these issues.

2 participants