|
From: frhamard <fra...@in...> - 2016-01-21 13:55:50
|
Hello, I post a question in link with this following topic (difference is the db): http://forums.jfrog.org/Artifactory-garbage-collection-is-already-running-td7579550.html I have 10 time bigger binaries space than artifact apparently due to the garbage collector which do not do its job properly. I am in version 3.1.1.1 with a derby database. What is the best strategy? -update software cause of a bug fix I do not know? -raise jvm memory? -export conf and repo and then reimport in a new database? -run a specific tool to clean binaries? Thanks in advance for your help. Hereunder my storage summary and logs when I restart the software : Binaries Count: 400,439 Binaries Size: 453.42 GB Artifacts Size: 25.56 GB Optimization: 1773.94% Items Count: 62,508 Artifacts Count: 42,152 -- View this message in context: http://forums.jfrog.org/Garbage-collector-never-stop-tp7580749.html Sent from the Artifactory - Users mailing list archive at Nabble.com. |