Hello Nick, first of all, it depends a little bit on how the frontend is implemented regarding its pipelines: if you cache pdf's in memory, or have extremely large results from pipelines in cache, you might use a lot of memory.
OTOH, I made the default settings for the caches to keep not very many items in memory, and start overflowing it to disk pretty fast. But, there might be other reasons that make your memory grow. For me, the status page is always quite informative about what is happening, but...you might have to know a little where to look, and what is means: this is not easy to explain For now, the easiest way to test it would be a profiler like yourkit. Do you have some sort of profiler to see where the memory is? Also 10 hits a second would seem to me that you have some parts not cached, because should be faster. Can you only test it at a JBoss instance, to rule out the container? Ard > > We have a Hippo frontend (hippo-cocoon-2.1.11) deployed on > JBoss and we are load testing it. The JBoss instance has 512 > MB memory. After slowly putting it under load, after 2 hours > we're at 600 requests per minute and it hung up with a > OutOfMemory exception. We have increased the memory to 768 MB > and the same happens but then on 660 requests per minute. > > Does someone have any pointers where to look to find where > our memory went? > > With regards, > > Nick Stolwijk > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
