Pretty much all that. Actual fetch within your worker comes out of the same machine. Puppeteer is ex
Pretty much all that. Actual fetch within your worker comes out of the same machine. Puppeteer is expensive, need to spin up an environment/isolate each user from each other, and rendering a page via Puppeteer in general is going to be way more expensive then a fetch of course, even locally it takes ~2s to get the html of google.com via puppeteer. iirc there's some interesting bits about knowing when rendering is done too which involve waiting for no activity. Also last I knew only Chicago was running browser rendering, at least back when it was just a workers binding.
It's just not really comparable, a single http request vs rendering a web page with all its resources
It's just not really comparable, a single http request vs rendering a web page with all its resources
