Some explanation.
Kosmos is caching two kind of data:
1. Java objects (the model itself) that represent SVN repositories in this case. These are
stored in the ehcache storage.
2. Generated content files (mostly images) that are charts in this case. These files must
be cleaned up, when a more uptodate version gets generated.
These are stored in the WebDAV storage (by default), and it might be expensive to delete
the files from those. The first time you launch Kosmos, there's nothing to clean, so
that's why it's faster. If you like, you can manually delete the stuffs from
WebDAV before starting up the container.
Of course, changing the ehcache configuration will not have any impact on the second.
And, 2 is pluggable, so you can use other mechanisms to store your images. (AFAIK the
JBoss Labs guys developed some custom solution based on their Shotoku for this purpose.)
I hope this helps to understand what's going on.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993287#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...