Re:Google Cloud vs. AWS Onboarding Comparison
by plasma on Wednesday February 24, 2021 @07:07PM
(#26258014)
I’ve been a long time Azure user, their SQL Azure product was very glitchy and had constant outages (“just add retries!”), it’s gotten better in the last year or so, but it was totally unacceptable.
[ Parent
| on HN ]
Re:Google Cloud vs. AWS Onboarding Comparison
by jiggawatts on Wednesday February 24, 2021 @07:24PM
(#26258171)
AFAIK that's a "feature", not a bug. They throttle concurrent requests and return a different error code compared to the on-premises SQL Server.
I just watched a load test hit that issue, the developers cranked up the traffic until the response times were measured in minutes. At that point Azure SQL started throwing errors related to too many concurrent queries.
Compared to just locking up or timing out, it's probably better.
See: https://docs.microsoft.com/en-us/azure/azure-sql/database/re...
And: https://docs.microsoft.com/en-us/azure/azure-sql/database/re...
E.g.: the 4-CPU pool has only 210 Max concurrent workers per pool, but if you think about it, that's over 50 queries running at once per CPU core, which is nuts!
Re:Google Cloud vs. AWS Onboarding Comparison
by plasma on Thursday February 25, 2021 @07:07AM
(#26262010)
I’ve experienced that too, but these errors were literally “server is currently unavailable” and downtime.
Ps: if you’re working on a production load system, and has decent traffic, lean towards premium/business critical tiers for true HA