Workers, Browser Run - Increased Browser Rendering limits!
1y ago
Source
CloudflareWorkers, Browser Run - Increased Browser Rendering limits!cloudflare.comBrowser Rendering now supports 10 concurrent browser instances per account and 10 new instances per minute, up from the previous limits of 2. This allows you to launch more browser tasks from Cloudflare Workers . To manage concurrent browser sessions, you can use Queues or Workflows : JavaScript export default { async queue ( batch , env ) { for ( const message of batch . messages ) { const browser = await puppeteer . launch ( env . BROWSER ) ; const page = await browser . newPage () ; try { await page . goto ( message . url , { waitUntil : message . waitUntil , } ) ; // Process page... } finally { await browser . close () ; } } }, }; TypeScript interface QueueMessage { url : string ; waitUntil : number ; } export interface Env { BROWSER_QUEUE : Queue < QueueMessage >; BROWSER : Fetcher ; } export default { async queue ( batch : MessageBatch < QueueMessage >, env : Env ) : Promise < void > { for ( const message of batch . messages ) { const browser = await puppeteer . launch ( env . BROWSER ) ; const page = await browser . newPage () ; try { await page . goto ( message . url , { waitUntil : message . waitUntil , } ) ; // Process page... } finally { await browser . close () ; } } }, }
You might also wanna read
Cloudflare Addresses CPU Performance Benchmarks for Workers Platform
Cloudflare investigated and responded to independent benchmarks by Theo Browne that showed Cloudflare Workers performing 3.5x slower than Ve
Single AI Agent Builds Functional Web Browser in Rust Over Three Days
A developer frustrated by the hype around Cursor's FastRender browser project (which used thousands of parallel agents to produce 1.6 millio
simonwillison.net·5mo ago

Comments
Sign in to join the conversation.
No comments yet. Be the first.