MINOR: [C++][CI] Bump ccache max size - #51259
Conversation
When trying to analyze the compilation caching behavior on apache#51255, I realized that our maximum ccache size of 1GB had become too small for some builds. The result is that a single build cannot be cached in its entirety, making identical rebuilds costlier than they should be.
9185f59 to
8c9bd91
Compare
|
Is there any specific log to look for to see this happening in the future? I am unsure I know how to find that this cache size has become too small. |
|
What I did is run a container locally, issued I'm afraid there's no easy way to automate such a hint on CI builds. |
|
How about monitoring build time or cache miss rate? FYI: Velox monitors build time (and build size): https://facebookincubator.github.io/velox/bm-report/ |
github-actions
Bot
added
awaiting merge
Monitoring build times would be interesting, but it needs someone to setup (and maintain the setup?). It would also require us to watch the results for deviations. |
3 participants
Rationale for this change
When trying to analyze the compilation caching behavior on #51255, I realized that our maximum ccache size of 1GB had become too small for some builds. The result is that a single build cannot be cached in its entirety, making identical rebuilds costlier than they should be.
What changes are included in this PR?
Bump ccache max size to 1.5 GB.
Are these changes tested?
Yes, by existing builds.
Are there any user-facing changes?
No.