Clearing an Oversized Cache

Artifactory Cleanup Best Practices

AuthorFullName__c
Patrick Russell
articleNumber
000004531
FirstPublishedDate
2019-08-23T07:13:48Z
lastModifiedDate
2025-08-03
VersionNumber
13

Artifactory's remote repositories store downloaded files in a cache. It’s generally beneficial to retain the entire cache as it speeds up downloads. However, if the artifacts being used for a given project change, you might find it worthwhile to periodically clear out the cache. If you’d like Artifactory to execute automatic cache cleanups for you, go to the Advanced tab of the remote repository menu. There, under Cache, in the Unused Artifacts Cleanup Period (Hr) section, you can define how many hours must pass, after which unused artifacts will not be deleted, but simply tagged internally as unused.


User-added image 

To configure and/or trigger this type of cache housecleaning, the cron job can be found under Admin > Advanced > Maintenance in Artifactory 6.X and Admin > Artifactory > Advanced > Maintenance in Artifactory 7.X. The Cleanup Unused Cached Artifacts field will, by default, execute a cache cleanup once every day.

 

JFrog Cloud Users

JFrog manages regular maintenance operations for all instances of JFrog Cloud. If you are a JFrog Cloud user, the features described on this page are all monitored and optimally managed for you by JFrog Cloud administrators.