I wasn't the one who deleted it, but I see that you advertised giving money for someone to help you.
I wasn't the one who deleted it, but I see that you advertised giving money for someone to help you. That's not allowed here.
V"motivating someone to help me ;D"
But noted.
Still are there some limitations on the Browser rendering ?
But noted.
Still are there some limitations on the Browser rendering ?
PHi! You can check the current limits here: https://developers.cloudflare.com/browser-rendering/platform/limits/ . Would love to learn more about your use-case and your feedback on the current offer.
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 …
KSeems like Node/Undici types instead of workers-types
J
XOops, didn't realize this was in beta, I wrote all the code already and realize I can't run it 
d85a0daa3e2452f1bcc7ba56d59ceb5eMissed that thank you!
VI am trying to make this via cloudflare workers. But sadly WebGL does not work in cloudflare
https://dev.to/rainerselvet/serverless-3d-webgl-rendering-with-threejs-4o11
https://dev.to/rainerselvet/serverless-3d-webgl-rendering-with-threejs-4o11
DEV Community
This image above was rendered in a serverless function on page load (not kidding, check the image...
PHey @vikiival | KodaDot , I believe you're right, but since that's not directly related to Browser Rendering, I would encourage you to post your question on the Workers channel in order to get a better answer regarding what you're trying to accomplish with WebGL 
J@Pedro You had mentioned that the team is working on updates to Session handling. Can you give us an idea on when those updates might be available? I understand that you probably can't be very specific, but are we thinking weeks? Months? Q1? Q2?. Can you give any sort of estimate?
PHey
PHey! if nothing unexpected comes up, late Q1 If you have feedback or ideas on how this should ideally work, please do pass them along
If you have feedback or ideas on how this should ideally work, please do pass them along JWhat I would like is to be able to start a "Durable Browser" and be charged per "Durable Browser" session started. CF would then handle all that behind the scenes stuff to keep the browser open and running (and restarting after crashes, or memory leaks, or whatever) and I don't have to worry about it. And then I can know in my code that I'm only registering 1 or 5 or 10, and then I can manage it accordingly. I'm not sure how that would work from a scalability perspective. But I can't stomach the volatility of either being charged pennies or thousands of dollars because of a memory leak in the browser, which I can't control, crashing and restarting. Or even things like deploying new code or attaching to the log viewer; if I understand right, my durable objects get reset; which starts a new browser session.
JI guess that's not super helpful. All in all, I don't really care about implementation details. I just need predictability in the pricing.
PThat's really helpful and aligned we our concerns. Thanks
Cquestions about sessions and number of pages and geography. I saw that for $5 a month you get 500 sessions. I was wanting to check multiple search results on certain google searches. 1. Is there a way to define the cloudflare geographic node making the remote request. 2. Is there a limit to how many pages I could view in a single session? 3. Can I block this service from other cloudflare customers using this on my domains? 4. (general puppeteer question..can't find a conclusive answer in google) Is there a good suggestion on how to add a simple timestamp to screen shot with the lowest overhead?
C(for #4, I injected a new div node with the time stamp before taking a screenshot and that solved my issue!) Now reading back about needing to create and keep open a durable object to maintain a single session if necessary to avoid going over 500 and seeing that it says open as long as there is not a empty 60 seconds. SO if I had had a cront job that checked perhaps a 100 pages with a sleep delay of 3 seconds to allow the content to load before doing a screen shot, and say this cron runs once a day then theoretically it can run 15 minutes giving me the opportuity to run 15 * 60 / 3 = 300 pages in a single cron job max per session
PHey @captain, you can indeed keep a session open using durable objects and check multiple search results with the same session. Please find an example here: https://developers.cloudflare.com/browser-rendering/get-started/browser-rendering-with-do/
- We are making changed to the product so that in the future you won't have to manage the DO and keepint it alive. We also have plans to add geolocation, so you can choose where the request will be originated, but it is not yet available in current beta. Thanks for sharing your solution for the timestamp
By following this guide, you will create a Worker that uses the Browser Rendering API along with Durable Objects to take screenshots from web pages …
Cthanks pedro for the update that's great to hear geo location and not have to manage a DO. I dont want to maintain a DO as its one more thing to think about (and haven't played with a DO yet...so far I'm rocking the D1 database and R2 storage)
EHey guys - I've signed up for the waitlist. Is there anything else I need to do to get access to the beta?
ZThere is! Put your account ID in this thread: browser-rendering-apiBrowser Rendering API Beta Access
Cwhy is puppetteer seeming way faster within the last 15 min?
G@jason did you figure out how to make it not take a screenshot of the full page?
GI was able to work around this bug by manually clipping the viewport which is a bit annoying but works.
Gthis does work, but scrollbars appear
Uso.. concurrency is very bad when using browser rendering DOs right? If two requests occur simultaneously, one will often overwrite the puppeteer "page" while the other is waiting for page load. What's the recommended way to avoid this? Durable Object input gates are not suitable for this purpose
Uis
blockConcurrencyWhileI was looking up the docs link for that haha. Yea, I believe that would work here. Alternatively, there's #queues-beta.
Uyeah that makes sense, I was also looking at queues and noticed they have customizable concurrency
ZAlthough I'm not entirely sure it's needed? Haven't played around with it too much, but would you not be able to get the existing browser, then create a new page, and use that page? I don't think that overwrites it?
Uyou're right, but eventually you'd have too many tabs open
Utabs == pages
ZYea that's true, although if you use something like queues you could prevent it from going over the specified concurrency
Uyeah, but im not sure how to figure out which page is safe to use
Ueven if concurrency is limited to, say, 5
ZWhy not have each process create a new page, then close it when it's done?
Ubecause what I wouldnt want is to send 5 concurrents reqs: pagecount = 5
send 5 more concurrent reqs: pagecount = 10
etc
send 5 more concurrent reqs: pagecount = 10
etc
Uyeah I need to make sure I can close by reference
Ue.g. that it's page.close() and not browser.close(4)
Uif former, then I think you're right
Uyeah ok so I think this works
UI wish there were some slightly more finegrained concurrency primitives, like a cross-worker semaphore
Ubut it's a bit niche and probably hard to implement
Uthanks for the help
Uqueues kinda do this but im hesitant to add more products
ZYea that's fair
Jhmm, semaphore-as-a-service market opportunity
D
A free API service for acquiring mutexes.
