3 ms·
I’m sorry you had that experience; your feedback is very helpful to us in pointing to where we can improve. Our storage layer which underlies the Basic tier has
by rachelagy 8y ago
I’m sorry you had that experience; your feedback is very helpful to us in pointing to where we can improve. Our storage layer which underlies the Basic tier has variable IOPS, and in this case it sounds like you were on the receiving end of a noisy neighbor. Our General Purpose and Memory Optimized tiers deliver more predictable IO and do not show the same behavior as the Basic tiers. That said we’re always working to improve all of our offerings, including Basic, and hope to provide a better experience for you in the future.
-Rachel, from Azure Database for PostgreSQL
- stevenjohns 8y agoI'm unsure why you're responding to this. There is no planet where 12 seconds latency is appropriate or a consequence of a "noisy neighbor" or not "predictable" or whatever you want to use to rationalise it. I don't believe your reasons because I had two Azure Database for PostgreSQL instances in two different locations (yes, I moved it across as part of troubleshooting) yet experienced the same levels of performance. The product that you charge ~$60 a month for is fundamentally broken. It is unusable for any application. If you are genuinely sorry, I'm happy to give you my company's contact details so you can refund or credit the last few months of what we paid for your service. Otherwise it's this type of empty response and lack of responsibility (or desire to correct the problems, or even correct your marketing material to emphasize what kinds of latency to expect) that led me to instruct my management and ultimately lead the move over to AWS.