This post discusses how a broken naming convention for releases in Sentry's database led to significant database performance issues, causing high CPU usage and timeouts. By identifying and capping problematic queries, the team drastically reduced CPU consumption and improved lookup times. The article dives into the technical details of the investigation, fixes implemented, and lessons learned regarding release naming and database management.