From: Wolfgang <wol...@ex...> - 2009-04-10 08:11:42
|
Hi Joe, > To answer your other question, my cacheSize in conf.xml is set as follows: > <db-connection cacheSize="48M" collectionCache="24M" database="native" > files="../exist-data" pageSize="4096"> Ok, those are the default settings, which are very conservative. They can't cause the memory issues. > One .xq that puts a particularly large load on the server is the page > that displays the indexes of our books (i.e. Afghanistan: p. 2, p. 4, > p. 32 ... ). Because these indexes are so long and contain so many > nodes, I've had to raise the watchdog limit to 50,000: > <watchdog output-size-limit="50000" query-timeout="-1"/> Depending on how you construct the XML output, memory consumption could be considerable, especially if you have many users accessing the pages. 512MB memory for the entire site could be a bit too moderate. I assume you are not keeping any other data in a HTTP session? I ask because this would further increase the memory footprint of your app. I could probably give you a better answer if I could look at the actual queries with a Java profiler. But I would need a copy of the queried data along with the real queries to do this. So if you want me to take a closer look at this, just give me a shout. > Would you suggest making any modifications to my settings in conf.xml? No, it looks ok for now. Once you have fixed the memory issue, you could even consider increasing the cacheSize. Wolfgang |