browser sessions start failing at around 20 concurrent. nobody warns you about this
Summary
Playwright scrapers in production on Node.js start failing around 20 concurrent browser sessions, causing memory spikes and crashes. The developer notes documentation does not warn about this limit.
Similar Articles
@browser_use: Here's 25 browsers starting in less than 1 second Enjoy
Browser Use launches a new browser infrastructure service featuring subsecond cold starts, lower cost at $0.02/h, and unlimited scaling, now live for developers.
@browser_use: https://x.com/browser_use/status/2066911791360422071
Browser Use Cloud rebuilt their infrastructure using Firecracker to reduce browser session costs from $0.06 to $0.02 per hour and achieve sub-second start times, while maintaining isolation and scalability.
stale html and headless browsers kept getting me blocked, so i started replaying the actual requests instead
The author shares their experience of switching from headless browsers to replaying direct requests to scrape websites, reducing block rates and resource usage significantly.
I benchmarked my browser agent against Browser Use on a live site (150 verified runs, same model). Sending page diffs instead of full re-renders cut token growth by 37%.
A developer benchmarks Rote, a memory manager for browser agents that sends page diffs instead of full re-renders, showing a 37% reduction in token growth compared to Browser Use, but with trade-offs on short tasks.
40% of my browser agent's sessions were silently failing and the LLM wasn't the problem
A developer discovered that 40% of browser agent sessions silently failed due to browser fingerprinting and automation detection, not LLM reasoning. An open-source tool called Leakish identified the issues.