document --shm-size and --cpus for consistent results #373
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.