数据库连接池
学习连接池如何消除每次请求都建立数据库连接的开销，以及如何调整连接池大小和参数以提升性能。
数据库连接池 是 CoddyKit 上的免费 System Design Basics for Backend Developers 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 System Design Basics for Backend Developers 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 System Design Basics for Backend Developers 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
The Cost of a Connection
Opening a database connection is expensive: a TCP handshake, authentication, and session setup can take tens of milliseconds. Doing this on every request adds latency and load you do not need.
What a Connection Pool Is
A connection pool keeps a set of open connections ready to reuse. A request borrows one, runs its query, and returns it — no setup cost per request.
- Lower latency
- Less load on the database
- A natural cap on concurrent connections
Borrow and Return
The lifecycle is simple: acquire a connection, use it, release it back to the pool. The critical rule is to always release, even on error, or the pool leaks.
conn = pool.acquire()
try:
conn.execute('SELECT 1')
finally:
pool.release(conn)Pool Size Basics
The key tuning knob is the maximum pool size. Too small and requests queue waiting for a connection; too large and you overwhelm the database with concurrent work and context switching.
Sizing the Pool
Bigger is not better. A common starting heuristic is based on CPU cores, not request count, because the database can only do so much in parallel.
cores = 4
# A popular rule of thumb (HikariCP):
pool_size = (cores * 2) + 1
print('suggested pool size:', pool_size)Queueing and Timeouts
When all connections are busy, new borrowers wait. Set an acquisition timeout so a request fails fast instead of hanging forever when the pool is exhausted. Surfacing the error early is better than a silent stall.
Connection Leaks
A leak happens when a borrowed connection is never returned. The pool slowly drains until every request blocks. Always release in a finally block (or use a context manager / try-with-resources) and enable leak detection in production.
with pool.acquire() as conn:
conn.execute('SELECT 1')
# released automatically on exitIdle and Max Lifetime
Tune connection longevity: an idle timeout closes connections the pool no longer needs, and a max lifetime recycles old connections to dodge stale sockets and server-side timeouts (e.g. a firewall dropping idle TCP).
Pools and Horizontal Scaling
Watch the math: 20 app servers each with a 50-connection pool means up to 1000 connections hitting one database — likely over its limit. Size per-instance pools with the total fleet in mind, or add a connection proxy.
instances = 20
per_instance = 50
print('total connections:', instances * per_instance)External Poolers
Tools like PgBouncer sit between apps and the database, multiplexing many client connections onto a few database connections. They are essential when you have many app instances or serverless functions that each open connections.
Tuning by Measurement
Do not guess. Monitor pool metrics — active connections, wait time, timeouts — under realistic load, then adjust size and timeouts. The right pool size is the smallest one that keeps wait time near zero.
Quick Check
Test your understanding of connection pooling.
Recap
You learned to optimize database access with pooling:
- Pools reuse connections to avoid per-request setup cost
- Size pools by capacity (e.g. cores), not request volume
- Always release; guard against leaks with timeouts and detection
- Account for total connections across all instances; use poolers like PgBouncer at scale
用 AI 导师学习 System Design Basics for Backend Developers — 免费
在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。
- 课程
- 12
- 课程
- 48
常见问题解答
「数据库连接池」课时是免费的吗？
是的 — 「数据库连接池」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 System Design Basics for Backend Developers 课程的其余内容，请升级到 CoddyKit PRO。 System Design Basics for Backend Developers 课程共包含 4 节课。
「数据库连接池」这节课中我会学到什么？
学习连接池如何消除每次请求都建立数据库连接的开销，以及如何调整连接池大小和参数以提升性能。 你通过在浏览器中直接运行的动手代码来练习 System Design Basics for Backend Developers，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 System Design Basics for Backend Developers 需要有经验吗？
无需任何先前经验。CoddyKit 上的 System Design Basics for Backend Developers 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「数据库连接池」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 System Design Basics for Backend Developers 课中编写并运行代码吗？
能。每节 System Design Basics for Backend Developers 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。