$FECRU_HOME/cache and $FECRU_HOME/var/cache are quite large

[Neeraj Sharma]

$FECRU_HOME/cache contains plugin caches and fisheye/crucible caches. As of now this cache size is close to 70B in our deployment. Can I get an insight of the content of this cache? Just plugin caching will definitely not take this much space.

Are these caches ever growing? If yes then eventually any box will run of space as cache size is always increasing. Why don't we have any cache eviction policy for these caches?

Also, doing an upgrade of exisiting instance of crucible with large caches is a challenge as copying and taking a backup of these caches is both time and space conduming.

[Sergey Svishchev]

$FISHEYE_INST/var/cache (which takes up most of disk space) is not actually a cache, it's a database (actually, a set of them -- one for each repository). Fisheye is entirely useless without them.

[Neeraj Sharma]

i know that /var/cache is svn cache. i am asking why $FECRU_HOME/cache is so large? wha if this cache is deleted? ho long does it take to build up again?

[Sergey Svishchev]

Its size somewhat depends on 'quality' of your svn repositories (i.e. how closely they follow the SVN Book branch/tag structure) -- see https://confluence.atlassian.com/x/eAbSEQ

Again, it's not a true cache -- more like a database index, in the sense that it either exists or isn't. But unlike a database table without an index, if you delete this cache, the repository isn't accessible (to Fisheye users) at all.

With a co-located repository (or a svnsync'd replica), about 3..10 milliseconds per affected path, and be aware that a 'svn copy' may affect your whole source tree.