Skip to content

Commit 2aa8203

Browse files
committed
connectionpooling
1 parent 66aeabf commit 2aa8203

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/mariadb/concepts-limits.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,11 @@ The maximum number of connections per pricing tier and vCores are as follows:
3232
When connections exceed the limit, you may receive the following error:
3333
> ERROR 1040 (08004): Too many connections
3434
35+
> [!IMPORTANT]
36+
> For best experience, we recommend that you use a connection pooler like ProxySQL to efficiently manage connections.
37+
38+
A MariaDB connection, even idle, can occupy resources. Also, creating new connections takes time. Most applications request many short-lived connections, which compounds this situation. The result is fewer resources available for your actual workload leading to decreased performance. A connection pooler that decreases idle connections and reuses existing connections will help avoid this. To learn about setting up ProxySQL, visit our [blog post](https://techcommunity.microsoft.com/t5/azure-database-for-mysql/load-balance-read-replicas-using-proxysql-in-azure-database-for/ba-p/880042).
39+
3540
## Storage engine support
3641

3742
### Supported

0 commit comments

Comments
 (0)