3 ms·
Sorry, I misworded. We are using it on "production", but our production is a closed beta for now, so we are using the Basic tier too. We are thinking in upgrad
by 101008 6y ago
Sorry, I misworded. We are using it on "production", but our production is a closed beta for now, so we are using the Basic tier too.
We are thinking in upgrade it to a better plan, but we are not sure because we are not sure that it will solve our problems.
I think that comparing to your own laptop is unfair because there is no connectino needed, everything is on the same CPU / RAM, etc. Remember when you connect to a external DB informatin has to travel from one point to another.
- Nextgrid 6y agoHopefully the Standard (or whatever they call it) tier will solve both our problems. If IO performance is the bottleneck (you can see it on the Azure console - in my case that graph goes up to 100% with very light use) then hopefully the next tier will solve it. > I think that comparing to your own laptop is unfair because there is no connectino needed, everything is on the same CPU / RAM, etc. Remember when you connect to a external DB informatin has to travel from one point to another. Yes indeed, but in my case I was talking about DB query performance where the network plays a minimal part. If a query is near-instant on my laptop I expect it to be the same (or better) on production infra, but with Azure's Basic tier I noticed the opposite. I agree that if you're firing off lots of queries then network latency starts to add up, but in my case I haven't even reached that point - network latency is insignificant compared to the actual delays I'm seeing on the individual queries themselves.
- nikita2206 6y agoConsider that even at the highest tier you’ll max out at 20k IOPS and the speed on these cloud services doesn’t generally go beyond 200MB/s. Now you can google how much IOPS and read/write speed a typical nvme SSD will give you, maybe you’ll reconsider using RDS-like services then