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
