assignUser commented on code in PR #13379: URL: https://github.com/apache/arrow/pull/13379#discussion_r897887033
########## ci/scripts/ccache_setup.sh: ########## @@ -23,4 +23,4 @@ echo "ARROW_USE_CCACHE=ON" >> $GITHUB_ENV echo "CCACHE_COMPILERCHECK=content" >> $GITHUB_ENV echo "CCACHE_COMPRESS=1" >> $GITHUB_ENV echo "CCACHE_COMPRESSLEVEL=6" >> $GITHUB_ENV -echo "CCACHE_MAXSIZE=500M" >> $GITHUB_ENV +echo "CCACHE_MAXSIZE=2G" >> $GITHUB_ENV Review Comment: > Yes, but what I mean is that if caches get evicted too often, then we won't benefit from caching :-) Yes, I understand but with the workaround to force `actions/cache` to update (and even before due to the key being pretty restrictive), we will have a lot of evictions. We could use an even bigger size and try to share ccaches between workflows by using similar keys, that way even if we have a lot of evictions the chance of a cache hit would still be high. Or would this cause issues with ccache? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
