Forums / Install & configuration / EZP 3.6.1 extremely slow make a Dual P4 Ibm server crash

EZP 3.6.1 extremely slow make a Dual P4 Ibm server crash

Author Message

H-Works Agency

Wednesday 08 June 2005 4:11:46 am

Config : Debian/apache/php/mysql/ezp 3.6.1.

After setting those var the server crashed :
- viewcaching = enable
- templatecache = enable
..etc in override/site.ini

Site : 1500 elements in contenu structure. This content structure is extremely slow to display (like 3 minutes !!!). Is there a way to hide certain classes identifier in the left menu. It should be the left menu that cause this slowness.

Thank for the help.

EZP is Great

Björn Dieding@xrow.de

Wednesday 08 June 2005 5:38:48 am

have you already looked in the contentstructuremenu.ini

This is new in 3.6

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Craig Hirsch

Wednesday 08 June 2005 6:22:44 am

Have you checked to make sure that you are not trying to reference the $node variable in your pagelayout templates? That can cause crashes when you turn on all of eZ's caching features.

What I did in a similar situation was to go through all of my pagelayout templates and ensure that every template variable I was using was a valid one for the pagelayout context. Once I did that, it solved the problem.

--
chirsch{AT}gmail{d.t}com

H-Works Agency

Wednesday 08 June 2005 12:27:38 pm

Thanks Bjorn for the Tips about the .ini file. It helped my a lot. Would be great if there was [sections] for each context. Like [content] to set up options for content left menu, [media] for media menu...Etc

Yes i am using the $node reference to retrieve my contents. What is the problem with it ?

Like a page title could be {$node.name} in a full view template.

Martin

EZP is Great

Vincent Lepot

Monday 13 June 2005 1:07:43 am

I've got the same problem for another site with more than 1500 entries in the tree. Content structure is so slow to build that I recommend to hide content structure to my users and to navigate using the children window...

Wouldn't it be great to have a tree which contains only "developped" elements and to refresh structure when clicking on a (+) or (-) button of the tree. At least, to have the choice.

I know that having all tree available avoids requests to the server, but with great trees, it's a big problem and loose of this functionality is too bad...