On 27.03.2008 00:31, Joerg Heinicke wrote:
Sure, here is the hierarchy from bottom to top. At this point, I ran
the test for about five
minutes (running longer would increase the percentage) and the
retained size of the one
ContinuationsManagerImpl object is 58% of the total. The
BufferedOutputStream is 50% of the
total, so the other 8% is consumed by the objects in between.
org.apache.cocoon.util.BufferedOutputStream
secureOutputStream of org.apache.cocoon.environment.http.HttpEnvironment
env of
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor$TreeProcessorRedirector
redirector of org.apache.cocoon.components.flow.java.ContinuationContext
What I was so much concerned about here was the fact of storing the
whole environment in the continuation, especially since we have this
non-flushing BufferedOutputStream at the end. Is there any point in
storing the environment? Do we get anything useful out of it after
continueing the continuation?
I committed a fix [1] that limits the data that is stored with the
ContinuationContext which at least removes the redirector and so the
BufferedOutputStream instances from the Continuation's memory footprint.
This should give you a big improvement if the BufferedOutputStream took
50% of the memory for you.
Joerg
[1] http://svn.apache.org/viewvc?view=rev&revision=642694
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
