CODEWITHSUNDEEP
mysqlperformanceazurescalability
Justin Skiles
Justin Skiles

Reputation: 9503

Scalability of MySQL on Azure

I'm using a MySQL instance on Azure under the free trial period. One thing I've noticed is that max_user_connections is set to 4 under this option and 40 under the highest priced tier.

Both of these seem really low, unless I'm misunderstanding something. Let's say I have 41 users making database requests simultaneously, wouldn't this cause a failure due to going over the max allowable connections? That doesn't seem like much room.

How can I use Azure to allow a realistic number of simultaneous connections? Or am I thinking about this incorrectly? Should I just dump MySQL for SQL Azure?

Thanks.

Upvotes: 0

Views: 743

Answers (1)

ron tornambe
ron tornambe

Reputation: 10780

If you are using the .NET framework, connection pooling is managed by the data provider. Instead of opening a connection and leaving it open for an entire session, with .NET each database operation/transaction typically opens the connection, performs a single task and then closes the connection after the operation completes. The .NET MySQL data provider also supports advanced connection pooling, see http://www.devart.com/dotconnect/mysql/docs/ComparingProviders.html

I would assume the Azure limitation is referring to applications that employ the first (session duration) alternative.

Upvotes: 1

Related Questions