How does connection pooling improve Flask app performance compared to opening a new DB connection per request?
easy📝 Conceptual Q10 of 15
Flask - Performance Optimization
How does connection pooling improve Flask app performance compared to opening a new DB connection per request?
ABy caching query results in memory
BBy encrypting all database traffic automatically
CBy reusing existing connections, reducing overhead of establishing new ones
DBy limiting the number of concurrent users
Step-by-Step Solution
Solution:
Step 1: Identify connection pooling purpose
Connection pooling keeps DB connections open and reuses them instead of creating new ones each time.
Step 2: Evaluate options
Reusing connections reduces latency and resource consumption. Encryption and caching are unrelated to pooling. Limiting users is not a pooling feature.
Final Answer:
By reusing existing connections, reducing overhead of establishing new ones -> Option C
Quick Check:
Pooling = reuse connections, less overhead [OK]
Quick Trick:Pooling reuses connections, saves setup time [OK]
Common Mistakes:
MISTAKES
Confusing pooling with caching
Assuming pooling encrypts data
Thinking pooling limits users
Master "Performance Optimization" in Flask
9 interactive learning modes - each teaches the same concept differently