<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build Performance on Support Tools</title><link>https://support.tools/tags/build-performance/</link><description>Recent content in Build Performance on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 30 Sep 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/build-performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Multi-Stage Docker Builds: Reducing Image Sizes by 800MB</title><link>https://support.tools/multi-stage-docker-builds-reducing-image-sizes/</link><pubDate>Wed, 30 Sep 2026 00:00:00 -0500</pubDate><guid>https://support.tools/multi-stage-docker-builds-reducing-image-sizes/</guid><description>&lt;p&gt;&amp;ldquo;Why does our container image take 8 minutes to pull in production?&amp;rdquo; This question from our SRE team kicked off an investigation that revealed our Docker images had ballooned to over 1.2GB - filled with build tools, test dependencies, and debugging utilities that had no business in production. What followed was a comprehensive optimization effort that reduced image sizes by 67%, improved deployment times by 75%, and strengthened our security posture.&lt;/p&gt;&#10;&lt;p&gt;This post details the journey from bloated single-stage builds to optimized multi-stage containers, including production-tested patterns, layer caching strategies, and the architectural decisions that make the difference between a 15-second deployment and an 8-minute ordeal.&lt;/p&gt;</description></item></channel></rss>