Forums / Developer / Caching 'includes' from pagelayout_section template

Caching 'includes' from pagelayout_section template

Author Message

Paul Forsyth

Monday 28 April 2003 7:30:13 am

We have a caching problem with includes from within a pagelayout_section.

The layout contains our design along with several includes for a header, footer and a leftmenu, eg:

{include uri="design:page_leftmenu.tpl"}

which picks up the page_leftmenu.tpl within the ''design/user/templates' directory.

As far as we can see we are using all caching options, for example:

ViewCaching=enableCached
ViewModes=full;sitemap
NodeTreeCaching=enabled

we tried adding more view modes to the list but this didn't seem to do anything.

With cache on we find that there are files within 'cache/template/tree' representing our included files. but within 'content/user/' there are only views for the full modes of the classes we are viewing.

As it stands our local machines give out about 30 pages a minute, largely due to the complex left menu we have designed. However, if we move the include for that left menu to the full view for a class and test again we find we get a 3 fold increase to around 90 pages a minute.

We would prefer not to move design elements into each full view in order to get this speed increase. Is there something we are perhaps missing from the ini files that would allow includes from the main pagelayout to be cached in the same way full views are?

btw, we are using php accelerator and ez rev 2356

Thanks

Paul

Paulo Almeida

Monday 28 April 2003 4:22:34 pm

Hi

Is this page_leftmenu.tpl the same o demo? If not could you publish? Do you use $node ?
I have a left_menu if pagelayout without problems.

Paulo Almeida

PACPI.COM Internet Consulting
http://pacpi.com

Paul Forsyth

Tuesday 29 April 2003 12:43:57 am

No, this is our own left menu template.

We don't have any problems with nodes and content but only with the page not being cached as efficiently as the full view. If you have cache on and look inside the php cache files that are generated inside the 'content' directory you will find that 'includes' from a pagelayout are not cached there.

Having an html/php cache for our complex left menu triples our page performance and allows us to meet our clients need for a high bandwidth site.

Paul

Paulo Almeida

Tuesday 29 April 2003 4:34:29 am

Have you tryed cache-block?
After using, i've get ~315 pages per minute, before it used to get <200.

But if you have a multi-site instalation, ez3 will create a fixed directory in var/cache/template-block, I've reported this bug to put template-block in cache directory of each site.

Paulo Almeida

PACPI.COM Internet Consulting
http://pacpi.com

Paul Forsyth

Tuesday 29 April 2003 5:42:19 am

Paulo,

Ahem, humble pie time.

Earlier we did try cache-blocks but didn't find that they worked. However, after trying them again today they now do work... One difference I tried was using an array for the key but im not really sure why that would make the difference. I probably made a mistake the first time. :(

Thanks

Paul