BYO Functions, Regions and Enterprise Edge
- Dominant language
- No language data
- Stars
- 346
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
While doing some performance testing of our app we noticed a few things that might be worth raising/getting advice around.
Firstly I know that SWA is a 'global' service, but what that seems to mean is it's hosted in a handful of azure regions and you're routed to the nearest one. It's not hosted in every azure region.
I'm in New Zealand, the closest azure reason for me is in Australia so I naturally put my BYO functions there. However the nearest SWA region seems to be HongKong. This means my traffic for API calls goes to HK then to AU then to HK then back to NZ, hosting the functions in HK makes a noticable difference to api response times.
Bare Functions AU - 50-70ms
Bare Functions HK - 160-170ms
SWA (pointing at AU) - 300ms
SWA (pointing at HK) -180-200ms
So immediately I figured I should probalby move my functions to HK.
I also tested using the enterprise edge function as that enabled 118+ locations (including AU and NZ) to the mix.
Static Content (Edge Disabled) - 150ms
Static Content (Edge Enabled)- ~50ms
API Content (Edge Disabled) - 300ms (as per above)
API Content (Edge Enabled) - 800ms
That's amazing for static content, but absolutely abismal for API.
Now i only waited for about 30 minutes after enabling before testing, but I did get a new IP for the domain so I figured it was enabled. Should it get better if I leave it longer?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.