I don't see how you can get a sub 100ms latency average over 5 hits if your cold starts are > 1s.
Maybe hitting the URL every 10 minutes keeps the URLs you test in your cache.
If users are frequently getting >1s due to cold starts and your stats are systematically excluding them, then the stats aren't very realistic.
I'm guessing you can see how many cold starts there were in AWS Lambda somehow... I can say anecdotally that I got slow responses several times from link.warpurl.com
> I don't see how you can get a sub 100ms latency average over 5 hits if your cold starts are > 1s
I can't and I am not trying to hide it, the CDN will keep a link in its Edge Cache for about 1 day. This is what causes the smaller spikes on the WarpURLs chart, the test link gets evicted from the cache and has to be looked up in the origin. WarpURL does not optimize for the first hit, but for the thousands that follow it near that PoP.
---
> Maybe hitting the URL every 10 minutes keeps the URLs you test in your cache.
No they stay at least 24 hours
---
>If users are frequently getting >1s due to cold starts and your stats are systematically excluding them, then the stats aren't very realistic.
Again, WarpURL does not optimize for the first/single click but for a single URL that gets thousands and thousands of clicks.
Maybe hitting the URL every 10 minutes keeps the URLs you test in your cache.
If users are frequently getting >1s due to cold starts and your stats are systematically excluding them, then the stats aren't very realistic.
I'm guessing you can see how many cold starts there were in AWS Lambda somehow... I can say anecdotally that I got slow responses several times from link.warpurl.com