Account ID is 397b462fa783ffd5a2e58c3a8fcd2f0a and worker name is `shopping-bird`
Account ID is 397b462fa783ffd5a2e58c3a8fcd2f0a and worker name is
shopping-bird
Vsure
Vraised
VHave you opened a support ticket? If not, could you please open it so that they can look into it?
JHow do I open a proper ticket? When writing it up I'm faced with
Customers on our Free plans can only submit tickets for billing, account, and registrar issues., even though I'm paying $5 a month for the plan with workers and DOVok, I'll have to open it for you internally, will give you an update on Monday
Ccan we request for the 2-browser limit to be raised on a per acct basis? if not, will this limit be lifted when you exit beta?
VDM'd you
NHey! I'd love to get access to the browser rendering api. Account: d0128033c48600d1b4c6f7106d4d8e55. Also, is there a tutorial on how to re-use a browser instance by storing it to DO?
Venabled
JCan you share any plans regarding amount of browser-limitations for free/paid plans when launching?
TThe Cloudflare Blog
We’ve heard from developers that configuring and maintaining their own serverless browser automation systems can be quite painful. The Workers Browser Rendering API solves this
ACool. Saw that my do was used in the post 
UIs the concurrent session pricing based on the peak concurrency during the month or do you have to pre-pay a set concurrency limit (and can you set a concurrency limit if it’s the first option?)
MAnd is that $1 each time you spawn a concurrent session or is that per month based on peak?
MWouldn't it be more cost effective to just keep a DO with a session alive perpetually? It costs just over $4 to keep a DO alive all month. If you use browser rendering just twice a day you're at $6/m (60*$0.10) in session costs. Setup a queue to process requests handled by that single DO and you never have to worry about having more than one session for an entrire month, correct?
AI also dont get the pricing. Would be great to get insights
UThe per session would be every time you call
puppeteer.launch(). You can reuse the session as explained with DOs in the blogpost which would make it where you can pay per minute with only the initial request warming up the DO costing or anytime the DO gets reset (should mostly code updates / runtime updates)ASo then keeping do alive would be cheaper right?
Udepends on your usage levels
DDoes puppeteer stealth work? (ping plz)
SHello. I'd like to get access to the browser rendering api. Account: 1448756027c02d2cb72a056a23538f40
SThank you
MFrom my understanding it would just be $0.10 every time the DO and browser session is instantiated as long as it's kept alive, so not even every day, as long as the browser instance gets a command at least every 60 seconds. If this is as it seems the pricing really doesn't make sense. Either there's an undocumented time limit on session time or the session pricing should be much lower to incentivize users to create new sessions rather than keep one open. Paying $0.10 once feels like a loophole.
If the best practice is to leave a session open, that should definitely be communicated in the pricing/docs since without considering using a DO, the pricing seems super high (who could justify $0.10 to take a screenshot when you can do the same thing with puppeteer on GCP functions or AWS for much much less).
If the best practice is to leave a session open, that should definitely be communicated in the pricing/docs since without considering using a DO, the pricing seems super high (who could justify $0.10 to take a screenshot when you can do the same thing with puppeteer on GCP functions or AWS for much much less).
Urequests != sessions
Ubut also 50 sessions would only be $5
Chey guy's made the request to get into this a while back...i even run a server using pupperteer as part of a workflow process...would love to start playing with this...been developing in workers for 2 years...any updates now that its in beta in getting access to this?
DHow does the concurrent session pricing work? Do I pay $1 to have the ability to run 2 sessions concurrently per month? (se then I can pay $5 for a concurrency of 6) Or is it $1 instead of $0.1 if there is already a session working? The blog post wasn't clear on that.
AThe pricing is confusing to me too.
What do I pay if I have one browser instance running all the time and it's constantly doing work (e.g. take screenshot of a page, one after the other .. all the time)
As I read it, that is one browser instance and one (concurrent) session, so the costs are 0 as the Workers paid subscription includes 500 Sessions and 10 Concurrent Sessions. Is this a correct understanding?
What do I pay if I have one browser instance running all the time and it's constantly doing work (e.g. take screenshot of a page, one after the other .. all the time)
As I read it, that is one browser instance and one (concurrent) session, so the costs are 0 as the Workers paid subscription includes 500 Sessions and 10 Concurrent Sessions. Is this a correct understanding?
PHello, looking for access to the Browser Rendering API. Thanks
ZPost your account ID in here browser-rendering-apiBrowser Rendering API Beta Access
VHi! Would love start using this API!
4dc10b1f5e6ded482cc85051fbdf49c9
4dc10b1f5e6ded482cc85051fbdf49c9
VAnd so the recommended way to use this service is to keep browsers alive as much as possible with Durable Objects?
ZLook one message above yours
VMy bad! Posted in the correct thread. My question still stands
VAlso, would love to know how one should handle large amounts of traffic, what would be the easiest way to build a queue
ZAFAIK yes, how the pricing works exactly is still a bit unclear, but it seems like there is little harm in keeping sessions open as long as possible to re-use them.
ZProbably #queues-beta
VLet's say I'm generating PDF of tickets, and an event goes live, 10k people purchase a ticket. I put each ticketId in the queue which gets consumed by a worker which is calling this API via a DO
Vbut that means there is literally 1 consumer for the queue running 1 request / sec (or worse if it takes longer)
VWhich would be really bad 
VOr I can actually fan out the work to multiple browsers, it's jut that it's going to cost a lot more?
ZYou can absolutely do that: Keep in mind that the current limits for the beta only allow 2 concurrent browsers (https://developers.cloudflare.com/browser-rendering/platform/limits/), and the current pricing (from https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects/) means that fanning out will increase the cost by quite a lot.
VYeah... so to keep using Cloudflare workers i'd need to write logic to fan out to a minimal amount of browsers but keep them 100% working all the time
