Document do not run LH in parallel
See original GitHub issueWas provided this repo: https://github.com/y-a-v-a/lighthouse-async
run it async to see the error:
lighthouse-async Error: no known mark: lh:gather:afterPass:OptimizedImages
lighthouse-async at Object.exports.stop (/Users/cjamcl/src/tmp/lighthouse-async/node_modules/marky/lib/marky.cjs.js:76:13)
lighthouse-async at Function.timeEnd (/Users/cjamcl/src/tmp/lighthouse-async/node_modules/lighthouse-logger/index.js:128:11)
lighthouse-async at Function.afterPass (/Users/cjamcl/src/tmp/lighthouse-async/node_modules/lighthouse/lighthouse-core/gather/gather-runner.js:407:11)
lighthouse-async at processTicksAndRejections (internal/process/task_queues.js:85:5)
lighthouse-async at async Function.runPass (/Users/cjamcl/src/tmp/lighthouse-async/node_modules/lighthouse/lighthouse-core/gather/gather-runner.js:665:5)
lighthouse-async at async Function.run (/Users/cjamcl/src/tmp/lighthouse-async/node_modules/lighthouse/lighthouse-core/gather/gather-runner.js:573:29)
lighthouse-async at async Function._gatherArtifactsFromBrowser (/Users/cjamcl/src/tmp/lighthouse-async/node_modules/lighthouse/lighthouse-core/runner.js:215:23)
lighthouse-async at async Function.run (/Users/cjamcl/src/tmp/lighthouse-async/node_modules/lighthouse/lighthouse-core/runner.js:81:21) +36ms
This is because the marks are stored in a global array, and gets cleared when a run finishes. If done while another run is between a start/end, the end will error.
I don’t believe we’ll fix the root cause here, since we do not support running Lighthouse like this. The suggested workaround is to run each Lighthouse run in a separate process. Even better, don’t run Lighthouse in parallel with itself - the performance metrics will be affected.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
17 Optimizer Hints
17. Optimizer Hints. Optimizer hints can be used with SQL statements to alter execution plans. This chapter explains how to use hints to...
Read more >LH - Linear Hashing for Distributed Files - Washington
LH * generalizes Linear Hsshing to parallel or distributed. RAM and disk files. An LH* file can be created from objects provided by...
Read more >Lustre Best Practices - HECC Knowledge Base
Accessing small files on the Lustre filesystem is not efficient. When possible, keep them on ... Run ls -lh to view the size...
Read more >Frequently Asked Questions - IQ-Tree
Perform 5 independent bootstrap runs (each with 20 replicates) on the 5 machines with 5 prefix outputs (such that output files are not...
Read more >recon-all - Free Surfer Wiki
-lh-crs C R S ... do not use the automatic subcort seg to fill ... lh and rh. This can be used to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think you should mention this on https://github.com/GoogleChrome/lighthouse/blob/master/docs/readme.md#using-programmatically
It might be nice to tell on that same documentation page how to do so.
Also nice to mention on that documentaion page, IMHO. Or even at the top of the readme.md
I think we have enough to close-close 😃 We can point people to this issue if it comes up again in the wild.