MySQL Connection Pool — Live
MySQL responsiveness
One-shot probe of the live database. Green < 10 ms, yellow < 50 ms, red ≥ 50 ms.
Pages that fire many small queries (Git_dashboard, audit-heavy hot paths) are sensitive to the SELECT 1 and audit-insert tiers in particular.
Pages that fire many small queries (Git_dashboard, audit-heavy hot paths) are sensitive to the SELECT 1 and audit-insert tiers in particular.
Pool acquire
—
get_connection() → handout
SELECT 1
—
network + auth round-trip
INSERT + DELETE
—
write path, scratch row
Audit INSERT
—
tblActivityLog hot-path simulation
never probed
Connections in flight
—
Pool size
10
Warn threshold
—
Lifetime acquires
—
never
In-flight connections, by caller
| Caller (file:function:line) | Held now | Lifetime acquires |
|---|
Held-connection ages (oldest first)
Anything older than a few seconds is suspect — well-behaved callers acquire and release in milliseconds.
| Caller (file:function:line) | Age (seconds) |
|---|
How to use this page:
Exercise the app, then watch this page.
A caller whose Held-connection count climbs and does not return to zero is leaking a connection.
Held-connection counts that climb and do not return to zero are leaking connections.
The backend logs a warning to
Raw JSON is at
Exercise the app, then watch this page.
A caller whose Held-connection count climbs and does not return to zero is leaking a connection.
Held-connection counts that climb and do not return to zero are leaking connections.
The backend logs a warning to
app.log at 8 of 10 in-flight, naming the top holders. Raw JSON is at
/admin/db-pool-stats.