This repository was archived by the owner on Aug 14, 2026. It is now read-only.
Benchmark Discourse's full Docker cache stack - #12
Closed
gauravtiwari wants to merge 17 commits into
Closed
Conversation
gauravtiwari
changed the title
gauravtiwari
changed the title
Contributor
Author
|
Closing this experimental image-factory branch. The full Docker layer, mount-cache, and ccache integration now lives in boringcache/discourse_docker, where the native base-image build can be tested truthfully. benchmark-discourse will stay focused on Discourse application work and only the caches that work actually needs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This benchmarks Discourse's full upstream base-image graph on native amd64 and arm64 runners.
It compares:
The jobs seed an older Discourse commit and roll one commit forward across the Aug 11/12 DATESTAMP boundary with unchanged Gemfile.lock and pnpm-lock.yaml. Targets run individually following discourse/discourse_docker#1088, using boringcache/discourse_docker#1 for the controlled cache wiring. BoringCache CLI is pinned to 1.19.1 and cache data is stored in discourse/benchmark-discourse.