Ron Blaschke wrote: > I've taken a quick glimpse at Forrest's memory usage, using the > lovely Yourkit Java Profiler (http://www.yourkit.com/).
Thanks a million. That is one of our important tasks. > I did the following: I ran "forrest site" in site-author/, and made a > snapshot, quite at the end of the run. Note that I have only limited > understanding of Forrest's and Cocoon's internals, so I might not have > interpreted things exactly right. > > The total retained size was about 63MB. There seem to be two > significant sources that eat memory. > > First, org.apache.cocoon.caching has a retained size of almost 22 MB. > Maybe it would be worthwhile to disable caching when creating a static > site? Cocoon will be using its cache during the processing run. So no, don't switch off :-) The cache system can be powerfully tuned and more efficient sitemaps will help. Forrest has not bothered to tune it until now. > Second, there are over 180 XML DOM documents > (org.apache.xerces.dom.DocumentImpl) eating about 29MB. They are > referenced by an instance of > org.apache.cocoon.components.modules.input.XMLFileModule. > These documents are referenced with URIs like: > cocoon:/pluginDocs/linkmap-index.html > cocoon:/linkmap-flyer.html > cocoon:/docs_0_70/linkmap-todo.html > cocoon:/versions/linkmap-index.html > cocoon://docs_0_80/linkmap-build.fo > cocoon:/docs_0_80/linkmap-primer.html > cocoon://dtdx/linkmap-document-v12.fo > ... > > It seems like these documents come from the "linkrewriter." Don't > know why these documents build up, though. > > I hope this information is useful to anyone. It sure is, thanks. Keep on. David
