Shared Puppeteer browser instance and concurrent page.goto: how should navigation queueing be handled?
I'm designing a scraping service that reuses a single Puppeteer browser instance (Chromium, recent stable version) and opens multiple pages to run page.goto() calls concurrently. Under low concurrency the behavior is fine, but as the number of simultaneous navigations grows, average navigation latency climbs well beyond the single-request baseline. My unders
puppeteer