2 ms·

You aren't crazy. I'd recommend testing from your app with a simple speed-of-light test (e.g., SELECT 1;) just in case your queries are slow. Perhaps Azure SQL

by boulos 10y ago

You aren't crazy. I'd recommend testing from your app with a simple speed-of-light test (e.g., SELECT 1;) just in case your queries are slow. Perhaps Azure SQL did the same thing we sadly did with the first version of Cloud SQL: run it in a totally different environment that requires you to go through several hops to reach the actual (MySQL in our case) server. But even then Cloud SQL First Generation was "only" 1ms away. Second Generation which runs in a VM but managed by Google (like RDS at AWS) is basically equivalent to running it on your own VM, and is thus about 100 microseconds away. Disclosure: I work on Google Cloud. PS. We recently launched SQL server images on GCE (https://cloud.google.com/sql-server/ https://cloud.google.com/sql-server/) though it's not a managed service (yet?).

mattmanser 10y ago
Yeah, that's how I figured out the cause of the problem. Had fixed a load of performance problems on a page, but couldn't get rid of 500ms compared to my laptop and realised it must be query latency and was surprised to see 100 "SELECT 1"s using the same connection consistently took 300-600ms (and it jumps around all the time in that range). The ridiculous thing is that the test server running on S1 has better performance (but still has a 200ms query lag for those 100). And that's leaving aside that heavier queries take 6 times as long on a so called "Premium" instance compared to my 2 year old laptop. Part of me suspects one of my cheap VMs running SQL Express could do better than azure's "premium" db performance. I also know it's not because of DTUs (MS's database usage metric), my client's site is seasonal and is just ramping up to prime-time, it had the same crappy latency in July when it was handling 1/10th the traffic as it has now.
- sljd 10y ago
  SQL Express has several performance limits and goes idle when not used.

by boulos 10y ago

mattmanser 10y ago

Yeah, that's how I figured out the cause of the problem. Had fixed a load of performance problems on a page, but couldn't get rid of 500ms compared to my laptop and realised it must be query latency and was surprised to see 100 "SELECT 1"s using the same connection consistently took 300-600ms (and it jumps around all the time in that range). The ridiculous thing is that the test server running on S1 has better performance (but still has a 200ms query lag for those 100). And that's leaving aside that heavier queries take 6 times as long on a so called "Premium" instance compared to my 2 year old laptop. Part of me suspects one of my cheap VMs running SQL Express could do better than azure's "premium" db performance. I also know it's not because of DTUs (MS's database usage metric), my client's site is seasonal and is just ramping up to prime-time, it had the same crappy latency in July when it was handling 1/10th the traffic as it has now.

sljd 10y ago
SQL Express has several performance limits and goes idle when not used.