Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caching uses too much memory #1825

Open
patrickersing opened this issue Feb 1, 2024 · 0 comments
Open

Caching uses too much memory #1825

patrickersing opened this issue Feb 1, 2024 · 0 comments
Labels
bug Something isn't working low-priority testing

Comments

@patrickersing
Copy link
Contributor

In TrixiShallowWater.jl I noticed error messages from julia-actions/cache@v1 that old caches could not be deleted. This seems to be solved by setting some permissions explicitly as suggested in https://github.com/julia-actions/cache.

I was wondering if this should be also done in Trixi.jl or why this is not frequently encountered in Trixi.jl. Looking at the CI runs there I saw that this happens rarely as here, but most of the times it says "No existing caches found".

The reason for this is probably that our caches get deleted by github because we use too much memory. Looking at the current cache status, a single test job saves a cache of around 1GB. If I am correct it means that even a single CI run creates around 20GB of caches, so twice our cache limit.
image

Github will then start to delete old caches until it reaches the 10GB limit. Besides that, from what I have seen all CI jobs can still load a cache (probably also because the limit is not enforced so strictly), so it doesn't seem to cause problems right now.

I still think it would be good to keep an eye on this and find some strategies to reduce our generated cache data.

@patrickersing patrickersing added bug Something isn't working low-priority labels Feb 1, 2024
@ranocha ranocha added the testing label Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working low-priority testing
Projects
None yet
Development

No branches or pull requests

2 participants