We are running into memory issues and it looks like wicket stores a lot of data in heap memory but also a lot of data is stored in session.
We aren't that concerned with page versioning or caching approaches. E.g. we can just turn all of that off. We thought about using setVersioning to false for all components. Also use the leastevictionstrategy and not use the secondlevelsessionstore.
In addition to that, we see one object that seems to eat up a lot of heap:
WicketApplication -> Settings -> MarkupCache$DefaultCacheImplementation
For this object MarkupCache, if we change the caching strategies, will the MarkupCache not fill up so much? Is there any setting that controls the MarkupCache?
Note: still using an old release 1.4.x (latest)
Berlin Brown
We aren't that concerned with page versioning or caching approaches. E.g. we can just turn all of that off. We thought about using setVersioning to false for all components. Also use the leastevictionstrategy and not use the secondlevelsessionstore.
In addition to that, we see one object that seems to eat up a lot of heap:
WicketApplication -> Settings -> MarkupCache$DefaultCacheImplementation
For this object MarkupCache, if we change the caching strategies, will the MarkupCache not fill up so much? Is there any setting that controls the MarkupCache?
Note: still using an old release 1.4.x (latest)
Berlin Brown