<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>DATABASE on Imran Khan</title>
    <link>https://imran-khan.com/tags/database/</link>
    <description>Recent content in DATABASE on Imran Khan</description>
    <generator>Hugo -- 0.127.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 29 Mar 2026 14:00:20 +0000</lastBuildDate>
    <atom:link href="https://imran-khan.com/tags/database/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your connection pool is too big or too small.</title>
      <link>https://imran-khan.com/posts/your-connection-pool-is-too-big-or-too-small/</link>
      <pubDate>Sun, 29 Mar 2026 14:00:20 +0000</pubDate>
      <guid>https://imran-khan.com/posts/your-connection-pool-is-too-big-or-too-small/</guid>
      <description>A few years ago I had an API that got slower and slower as traffic went up, which is normal, except the database was sitting at about 20% CPU the whole time. I stared at query plans for two days. Added indexes that didn&amp;rsquo;t need adding. Eventually someone looked at my code for thirty seconds and asked why I was opening a new database connection inside the request handler.
So. Connection pooling.</description>
    </item>
  </channel>
</rss>
