{
  "id": 9506643,
  "title": "We spent thirteen weeks about to buy a bigger database",
  "url": "https://urgent.news/2026/09/24/we-spent-thirteen-weeks-about-to-buy-a-bigger-database",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-24T06:54:00.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/sergey_shinder_ab2d943365/we-spent-thirteen-weeks-about-to-buy-a-bigger-database-3i66"
  },
  "original_language": "en",
  "account": null,
  "summary": "The article discusses a case of misattributed database performance issues at a company that spent thirteen weeks attempting to improve query times. Despite various optimizations, including adding indexes and rewriting joins, the p99 database time remained at nine hundred milliseconds. The issue stemmed from the instrumentation, which was incorrectly attributing connection wait times to database query duration. The root cause was traced back to a single endpoint that opened a transaction, called an HTTP rendering service, and held onto the connection for up to eight seconds while waiting for a PDF. This accounted for forty calls per minute, significantly impacting the perceived performance of other queries. The solution involved refactoring the instrumentation to separate connection acquisition and query execution into distinct spans, providing a clearer picture of the system's performance.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}