AI was told I can request for the beta access over here!
ACan I get access for this Account ID: 6413bfbe023fbf879350a20fe7a2245b?
C
Put your ID in the thread for access here: Browser Rendering API Beta Access (can also be found via pins)
Aalright!
JHello, I'm trying to understand the proposed pricing structure and how to optimize it. Based on the proposed pricing in this blog post[1], you get 500 sessions per month for free and then 10 cents per session after that. A session, as I understand it, is an active running browser. The naive approach, at any sort of scale, quickly becomes expensive. So the blog says to use a durable object to keep the browser alive and re-use the existing session instead of starting a new one. The example code uses an alarm to keep the browser alive while idle for 1 minute before shutting it down. Using this structure, If I'm understanding it right. Worst case scenario, if I had a job that triggered every 61 seconds, I'd end up starting about 1440 sessions per day. Which is $144/day or over $4k/mon. That's expensive. So, the solution would be the extend the life of the durable object to, say 2 minutes, which would reduce the $4k to $0, for the browser cost.
However, the durable objects aren't free, but I'm having a much harder time understanding how expensive they will be. For example, why do I need to shut down the browser at all? How much does it cost for the browser to sit idle in a Durable Object? Is that documented anywhere? And what if it's not idle? If my worker is handling 1 request per sec, so the browser is in active use all of the time, what sort of costs is that going to yield for the DO?
Any information would be appericiated.
[1] https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects/
However, the durable objects aren't free, but I'm having a much harder time understanding how expensive they will be. For example, why do I need to shut down the browser at all? How much does it cost for the browser to sit idle in a Durable Object? Is that documented anywhere? And what if it's not idle? If my worker is handling 1 request per sec, so the browser is in active use all of the time, what sort of costs is that going to yield for the DO?
Any information would be appericiated.
[1] https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects/
MIt costs about $4 to keep a DO alive an entrie month but I'm not sure if that's somehow against terms for browser rendering or if there's unintended consequences.
browser-rendering-api
As far as understanding the pricing I've got no clue and there hasn't been any real clarification on that. Not a single use case makes sense to pay $4000 per month for a single browser instance. You could hire a human for that.
browser-rendering-api
As far as understanding the pricing I've got no clue and there hasn't been any real clarification on that. Not a single use case makes sense to pay $4000 per month for a single browser instance. You could hire a human for that.
JThanks for the reference to those previous messages. I'm glad that I'm not the only one who is confused by all of this.
JSome people were mentioning that having one session open, means one request at a time, but that's not true. You can use
newPage() to use the same browser to process request async - but there's got to be some limit to that. I can't imagine one browser would do 100s of request simulateously. But again, those limits don't seem documented either.
USeeing as the blog post about browser rendering showed how to keep sessions alive with a durable object I would find it highly unlikely to be against TOS 
JThe question is whether keeping the browser open indefinitely is against the TOS. The blog shows how to shut it down with an alarm after a certain amout of time.
UIf you dont do a request to the session in 60 seconds it shuts down thats why they destroyed it after 60 seconds so you dont get billed for the DO being alive if the session isnt even active anymore
UIf you do a call every 60 seconds their example would live forever
JWhere is it documented that the session shuts down automatically after 60 seconds?
Uhttps://developers.cloudflare.com/browser-rendering/platform/limits/#limits
A browser instance gets killed if it does not get any command for 60 seconds, freeing one instance.
The Workers Browser Rendering API is currently in beta. Add yourself to the waitlist to reserve your spot, and as we expand availability, we will …
J@Unsmart | Tech debt Ah, okay. That's not good at all then.
JSo if you have, in my example a service that gets a request every minute in a half, you'll have to start a new session for each request.
JWhich will end up with a $4k bill each month.
JYou'd want to add a heartbeat request every <60s in order to keep the browser alive to avoid starting new ones. Crazy.
MYep. The problem isn't keeping it alive for a minute but if it's okay to keep it alive for forever. And if so why is that the best practice, seems hacky.
It doesn't make sense that CF needs to charge $0.10 to spin up/spin down a browser rendering instance for 60 seconds but will let you keep it up all month for $0.10 as long as you interact with it once every 60 seconds. The economics just don't make sense.
It doesn't make sense that CF needs to charge $0.10 to spin up/spin down a browser rendering instance for 60 seconds but will let you keep it up all month for $0.10 as long as you interact with it once every 60 seconds. The economics just don't make sense.
JAgreed. Unless it's basically free for them to have it sit idle... but if that's the case, why automatically turn them off after 1 minute?
MYeah or just make the session pricing low enough so that it makes sense to spin up/spin down as needed rather than relying on hacks to avoid a $4k bill.
JDo CF devs monitor this channel? Or is it only community members speculating? 
AIt's a very puzzling situation. I'm basically waiting until it's sorted out before I implement anything with the Browser Rendering API
HHey there when using the Browser Rendering API, I ran into a cloudflare challenge on a website I wanted to access lol. Is there anyway to wait/bypass that? Or is this a goner? Thanks!
HHey Dan did stealth work out for you?
DI haven't tried it, I don't think anyone answered my question on pricing so I didn't try it
DI think that's the point, they don't want bots
HThat's a bummer... will probably have to work a way around then. Thanks for answering bro!
VIs this supposed to work on Pages function?
PHey @jasonlfunk, currently, on the free plan, each account can initiate up to 100 browser sessions per month.
For the Paid plan (included in Workers), each account can initiate up to 500 sessions/month with the capability to run 10 concurrent sessions. Additional sessions on this plan are billed at $0.10 each, and additional concurrent sessions costs $1.00 each.
Each account can start up to two new browser sessions every minute. Note that if a browser instance remains idle, with no commands issued for 60 seconds, it will be terminated, thus making room for a new available instance.
Durable Object enables the creation of a "continuous browser session". This approach allows for the reuse of a browser instance without incurring costs for starting a new session, though charges for the Durable Object apply
For the Paid plan (included in Workers), each account can initiate up to 500 sessions/month with the capability to run 10 concurrent sessions. Additional sessions on this plan are billed at $0.10 each, and additional concurrent sessions costs $1.00 each.
Each account can start up to two new browser sessions every minute. Note that if a browser instance remains idle, with no commands issued for 60 seconds, it will be terminated, thus making room for a new available instance.
Durable Object enables the creation of a "continuous browser session". This approach allows for the reuse of a browser instance without incurring costs for starting a new session, though charges for the Durable Object apply
UBased on this message I assume you work at CF. As an fyi you can run the
/cfrole command to get the cloudflare employee role JI understand. I think the outstanding questions are this:
1) Is it a problem to keep a browser session open indefinitely? (by using alarms/cron to keep it active).
2) How many pages can a single browser session reasonably have open at a time? (If my app is processing 100 requests per second, can they all be sent to a single session? Should they be split up over multiple sessions?)
1) Is it a problem to keep a browser session open indefinitely? (by using alarms/cron to keep it active).
2) How many pages can a single browser session reasonably have open at a time? (If my app is processing 100 requests per second, can they all be sent to a single session? Should they be split up over multiple sessions?)
PWe are currently in beta and things might change, but 1) As shown on the previously mentioned blog post, it's acceptable to keep the session active. 2) I'll need to verify and follow up regarding your second question, but it seems the limitations will likely be tied to memory capacity, which can vary with each use-case
JGreat, thanks for the information.
VDoes this means, it cost me $3,880 per month for single URL screenshot every minute?
For example, if I have a worker capturing a website screenshot on every minute scheduled CRON.
(43,800 minutes/session * $0.10 per session) - 500 free session = $3,880
It's going to be super expensive
that way. What are other suggestion?
For example, if I have a worker capturing a website screenshot on every minute scheduled CRON.
(43,800 minutes/session * $0.10 per session) - 500 free session = $3,880
- Assuming a new session will be created each time the scheduled function starts.
It's going to be super expensive
that way. What are other suggestion?PHey @Vikash [Agenty], consider using Durable Object as a way to reuse the open sessions. Please take a look at this blog post, as the example seems quite similar to your use-case: https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects/
The 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
VIf I use durable object and keep setting the alarm. Does that mean my session will never expire? Because I am using CRON so it will keep warming up every minute
VAlso, any way to track cost/sessions in beta?
PMostly, note that the Durable Object might be terminated in some instances, such as if it is idle for 30 seconds, if it hits memory limits or when we put out new releases
PNot something we offer at the moment, but we are exploring this possibility
DHello, I would like to request access to the browser rendering API. Thanks!
ZPut your account ID in browser-rendering-apiBrowser Rendering API Beta Access
DThanks!
JWow, I joined this Discord to learn more about the Browser Rendering API. And I'm shocked about the pricing! 
For 5 USD i can execute a simple docker container, that might does not scale, but that wouldn't introduce a private bankruptcy...
For 5 USD i can execute a simple docker container, that might does not scale, but that wouldn't introduce a private bankruptcy...
UBy following this guide, you will create a Worker that uses the Browser Rendering API along with Durable Objects to take screenshots from web pages …
Uis the example code above correct? The browser instance is unconditionally closed in fetch(), which makes the durable object useless for the next call
U@Pedro
Uactually this example seems to have lots of mistakes 
Jhave you figured out how it should be implemented instead?
Uat a minimum:
- remove the
browser.close()line - check that the browser is connected every fetch (
this.browser.isConnected()), and reinstantiate it if not - do not call newPage() every fetch, instead check the browser instance and see if it has the number of pages you need already, from last time
- add an await to the setAlarm call
state.blockConcurrencyWhile() may be the answer, but I haven't tested it yet