Hi JC, If those 7 shoot-boxes contain a lot of items maybe you need to change your template. Maybe things will speed up a bit if you use the listitempreview widget [1] instead of the shootbox. However for the display of the values you've chosen the CMS still needs to load the full lists.
If that doesn't help try to increase the memory settings to: maven.wrapper.maxmemory=512 maven.cocoon.heapsize=500600000 cms.eventaware-store.maxobjects=30000 maven.jetty.maxformcontentsize=1000000 [1] http://www.hippocms.org/display/CMS/Layout+reference#Layoutreference-Lis titempreviewwidget Jasha Joachimsthal [EMAIL PROTECTED] - [EMAIL PROTECTED] www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100 +1 (707) 773-4646 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Hippo WCMTech > Sent: donderdag 20 november 2008 18:20 > To: Hippo CMS development public mailinglist > Subject: [HippoCMS-dev] [CMS+REPOSITORY] Multiple > Dynamic-content in abackend ==> Big Performance Issue ?! > > Hello Hippo addicts ! > > We have a back-end template with 7 shoot-boxes that's > retrieve items from the repository content (like documents > lists, users list,...). The documents (> 2000) are divided > into several folders, several trees, binaries too. Each > shootbox is filled with dasl requests (in > extensions/project-specific/dynamic-content/), those requests > have corrects targets (not directly on preview for example), > corrects parameter (uid,...) and work perfectly when we call > it directly in the browser. > > Our caching seems correctly setted too, repository config also. > > However, we have big performance problems atm; very long time > to respond, huge garbage collecting, proxy errors, etc... > > We are working on it since few days without success but only > the idea that's can come from the dasl queries... > > > Can you eventually advice us about that problem ? Like > typical configuration for "big" CMS, any advice or idea will > be good for us now ;) > > Thank you in advance ! (sorry for my limited english) > > JC'n co > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
