From 44d34874025359ddd48557a50a873199813212c5 Mon Sep 17 00:00:00 2001 From: FosterStack Admin <317177128+fosterstack-admin@users.noreply.github.com> Date: Thu, 8 Oct 2026 20:22:38 -0400 Subject: [PATCH] Page: how big a server does a build cache need --- build-cache-server-sizing/index.html | 131 +++++++++++++++++++++++++++ sitemap.xml | 4 + 2 files changed, 135 insertions(+) create mode 100644 build-cache-server-sizing/index.html diff --git a/build-cache-server-sizing/index.html b/build-cache-server-sizing/index.html new file mode 100644 index 0000000..ce8cbfb --- /dev/null +++ b/build-cache-server-sizing/index.html @@ -0,0 +1,131 @@ + + + + + +How big a server does a build cache need? CPU, RAM and disk + + + + + + + + +
+ +
Infrastructure worth keeping — and kept patched.
+
+
+

How big a server does a build cache need? CPU, RAM and disk

+

You are sizing a disk, not a compute tier. The server is one small program that idles in tens of megabytes, so the question is how much cache you want to keep.

+ +

Starting sizes

+ + + + + +
vCPURAMDisk
Absolute minimum11 GBcache cap + about 5 GB for the system
Recommended start, about 5 to 20 developers plus CI1 to 22 GB25 to 50 GB SSD
Larger CI farms2 to 44 to 8 GBcache cap + about 20%
+

These are starting points from our deployment guide. Your build graph decides the rest. It is hard to be limited by CPU, because the busy path is reading and writing stored files, not computing.

+ +

Set a size cap

+

Choose how much cache you want, set it with FSCACHE_MAX_BYTES, and make the disk about 20% bigger. When the cache reaches the cap it removes the least recently used entries and never grows past it. The extra room covers file system overhead and uploads in progress.

+

The value is in bytes. It is easy to be wrong by a factor of 1024, so copy one:

+ + + + + + +
CapFSCACHE_MAX_BYTES
10 GiB10737418240
20 GiB21474836480
50 GiB53687091200
100 GiB107374182400
+ +

Two mistakes that look like "the cache doesn't help"

+ + +

Put it near the runners

+

On bigger setups the network matters more than the processor. A small server in the same region, ideally the same network, as your CI runners beats a large one far away.

+ +

Related: Gradle and Maven setup and Jenkins and CI build cache. Full detail is in the Docker deploy guide.

+
+ Gradle and Maven setup + FosterStack home +
+
+ + + diff --git a/sitemap.xml b/sitemap.xml index 8c1e470..9ecdf10 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -16,4 +16,8 @@ weekly 1.0 + + https://fosterstack.com/build-cache-server-sizing/ + 2026-10-08 +