Hey guys! I'm using pants with a remote cache (I ...
# general
h
Hey guys! I'm using pants with a remote cache (I have 380 packages I'm trying to test -- hence the remote cache) All is fine running locally, but github-runners always run out of space on CICD Any tips for better managing disk space? So far, I've played around with these settings, but to no avail (maybe the need to be lower?)
Copy code
local_store_directories_max_size_bytes = 5000000000
local_store_files_max_size_bytes = 5000000000
local_store_processes_max_size_bytes = 5000000000
f
sorry if I misunderstand, but you are using remote cache, would you consider disabling local cache so it's not being used at all? Given the access is configured properly and you are not transferring hundreds of megabytes as artifacts, you could just rely on the remote cache and have local cache disabled, see https://www.pantsbuild.org/2.18/reference/global-options#local_cache. If your CI builds take place in a fresh environment (i.e. each build starts a new container with no local cache), then IIUC the local cache will only be shared between Pants calls in your build. Maybe it's worth checking the performance of your builds in CI with local cache disabled to confirm relying on remote cache only is feasible?
h
Wow, I just assumed the local cache would be disabled if I had configured a remote cache haha
This makes a lot of sense, I'll try this!
🙌 1