Argo Cloudflare Routing

I’m still learning a lot about hosting & site performance. While I previously thought I had it all figured out through a single fast server, I was surprised to see really poor results in some TTFB checkers, especially for longer distances (even though the speed of light latency is not that high in theory).

I was getting much lower than expected results anywhere outside Europe (my server being in Amsterdam):

It turns out much of it has to do with internet routing. I don’t really understand how all that works but apparently the exact path the request takes matters much more than the theoretical latency implied by the distance itself.

I enabled Cloudflare Argo Routing ($5/mo + $0.1/GB) and interestingly it makes a huge difference.

After enabling it:

All of that said, it seems nothing beats a static site that is fully cached via Cloudflare Edge. While the above results are for my uncached demos, this is for my 100% cached site:

1 Like

Nice results. I never tested Argo, I am personally in the ā€˜free service’ mindset when it comes to Cloudflare, I never paid them a dime. :))

Also, I am a bit disappointed of their max wait time for server response of 100 s, which in some cases can be deal breaking…

The Enterprise ppan allows extending this, but only a bit…

Anyway, this topic is about perf, so yeah, the Argo seems to be of use in this case.

Yeah Cloudflare free already does so much. I’m just a beginner at this and trying out every option and learning - this is something I really love about AI, it’s teaching me so much in a way I could have never learned just by endlessly reading through reddit threads.

Care to explain that a bit?

Well, if you are using long lasting Ajax calls on your server and you are using Cloudflare, you are in bad luck, as they will block everything which runs longer than 100 seconds, after which they throw an error 524.

Also, they state that this is not configurable unless on the Enterprise plan (which is very expensive). https://community.cloudflare.com/t/increase-cloudflare-max-request-duration/482873

Only option is to turn off Cloudflare proxyfication of your domain/subdomain or make your requests faster/chunked…

1 Like

Ah, I was so confused about how the limit could be 100ms, then I realised it’s SECONDS. Maybe the solution in these cases is to split a large request into multiple smaller ones, e.g. similar to Importer tools

1 Like