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
Should we increase default timeout? #20
Comments
Yes, the timeout applies to the various 'modes' of the goto function.
It depends. Maybe its good to just set it to 1 min. For sites that load quickly, there should be no affect.
They would not be included in this.. There will be separate logic, part of #9, to handle waiting for video playing. Also, the timeouts could be for any number of reasons.. for example, I've seen more timeouts when too many browsers are running and there is not enough CPU.. |
OK, thanks for the details. I think we should increase the default then. Maybe 90s? I think we shall also document in the You mentioned the separate behavior for video but what about non-video resources? Images, or large non-media files like JS or WASM files? Is there a timeout at play there? Thanks for pointing to the concurrency issue ; indeed that must be taken into consideration when writing recipes. Network is also affected although I understand for most cases, bottleneck would be CPU. |
Scraping fondamentaux, I got a lot of timeouts on pages (169!) with the default 30s timeout.
@ikreymer could you please give us more details on the implication of timeout:
await page.goto(url, {waitUntil, timeout});
implies it's the time for the page toload
(that's the defaultwaitUntil
value). Is this the time before the document loaded event?My initial though would be to use a large value here to capture long pages and other pages would still load and be processed fast.
The text was updated successfully, but these errors were encountered: