Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

WordPress

MySQL connection limits: diagnose too many connections safely

Published August 2026 · 2 min read · Updated 2026-09-05

MySQL connection limits protect the database from unbounded sessions, but hitting the limit is usually a concurrency or lifecycle problem. Raising max_connections without checking per-connection memory, query latency, and application pooling can turn a clean “too many connections” error into memory pressure or a slower database.

Measure active versus sleeping connections

Inspect current sessions, connection rate, Threads_connected/Threads_running equivalents, long-running queries, sleeping duration, and connection errors. Hundreds of idle persistent sessions are a different problem from hundreds of active queries.

Map sessions to applications/users/hosts so one pool can be identified.

Calculate concurrency from request behavior

Web applications often open database connections per worker/request. More PHP workers can therefore increase database concurrency. Queue workers, cron, admin jobs, and monitoring also contribute.

Fix slow queries because shorter query time returns connections to the pool faster.

Use application pooling and sane timeouts

Persistent connections can help or hurt depending on runtime and pool design. Configure pool maximums below the database ceiling with room for administration and maintenance.

Avoid extremely long idle timeouts when clients do not need persistent sessions.

Raise the server ceiling only with memory headroom

Estimate connection-specific buffers plus global database memory and observe real process RSS. Increase max_connections only when legitimate concurrency requires it and the server can handle the memory/CPU/query load.

  • Separate active from sleeping.
  • Map sessions to workloads.
  • Bound application pools.
  • Protect memory before raising max_connections.

Next step

Separate active from sleeping sessions, inspect pools and slow queries, and account for per-connection memory before raising the database connection ceiling.

Explore DotMoose WordPress hosting

Keep reading

Related guides.

Do I need web hosting for WordPress? What WordPress actually needs

Self-hosted WordPress needs web hosting, but it does not require a specially branded WordPress plan. Compare WordPress.com, regular shared hosting, WordPress hosting and VPS options.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

PHP timeout troubleshooting: PHP, PHP-FPM or the web server?

Find which PHP timeout fired, check the right configuration, and distinguish PHP execution limits, PHP-FPM termination and nginx FastCGI read timeouts.

Read the guide

More wordpress guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move