On Thu, 10 Jul 2008, Johan Compagner wrote:
try it with yourkit?
I've got JProfiler and at least with that it's been a bit
difficult to pinpoint which exactly are the components
hanging onto the biggest objects.
But I did a kludge in our own DiskPageStore extension where
I visit all the
This also revealed that for example the page instance I'm
currently looking at has more than 2000 components in total
:) Maybe we should look at replacing some stuff that is not
displayed with dummy WebMarkupContainers instead of relying
on visibility control.
Maurice and Martijn have a
try it with yourkit?
i know it is still a bit of work but normally if you do a request and after
the request you look at the HttpSession
and see how big it is, you should be able to pin point the biggest retained
size
johan
On Thu, Jul 10, 2008 at 5:24 AM, Timo Rantalaiho [EMAIL PROTECTED]
Hello,
I'm currently debugging a situation where we have too much
data in the session (in some places, more objects should be
behind detachable models, smaller object graphs retrieved
from the db etc). I've added debug logging to get the size
of the page just before storing it in DiskPageStore
