Avoiding waterfalls
I've got a website on pages. It has some backend logic, and also calls an api. The api is hosted on workers.
From what I understand, the cold start for the website should be very minimal because it's warmed during https handshake. That request alone is around 300ms, which is ok.
The website then needs to call the api. Again, this has around 300ms warm up. Now the total for the request to the website ends up around a full second. That's way too long. If I could pre-warm the api when warming pages, I think I can save at least 300ms.
How do I avoid waterfalls?
From what I understand, the cold start for the website should be very minimal because it's warmed during https handshake. That request alone is around 300ms, which is ok.
The website then needs to call the api. Again, this has around 300ms warm up. Now the total for the request to the website ends up around a full second. That's way too long. If I could pre-warm the api when warming pages, I think I can save at least 300ms.
How do I avoid waterfalls?
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,425Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
