This message was deleted Gradle Community #caching

Join Slack

This message was deleted.

# caching

Slackbot

04/20/2022, 2:02 PM

This message was deleted.

Roldan Galan

04/21/2022, 8:57 AM

AFAIK local cache has eviction date, but remote cache will keep the artifacts until there is no more space, and they I assume then they are removed based in Least Recently Used.

Roldan Galan

04/21/2022, 9:02 AM

We had the same feeling recently (that the cache items ware lasting just a few hours) and we increased our remote cache by 10x and found a huge boost of performance in all our builds. We monitored the

your-domain/cache-admin/

during the process and with that increase the cache took around a day to start evicting artifacts again. We moved from 82% hit ratio to 96% just with this little change. Also now our building time stats are smoother as now the cache is constantly there. Before we used to have big valleys for builds finding most cache hits and big peaks when the required entries were already evicted.

Roldan Galan

04/21/2022, 9:02 AM

Said that, it would be really cool to have a way in gradle enterprise to easily display the date of the eldest item, to have a clear idea instead of figure out that through experimentation.

Ben Poland

04/21/2022, 3:43 PM

Thanks, yeah I read a doc that said the remote cache uses the LRU algorithm. And yes, I would be interested in stats about how long things are generally staying in the cache to help tune. For now I think we are going to just blindly increase the size and see if that helps our hit rate (currently 94%)

Open in Slack

Previous Next