Friday 16 December 2005 10:22:49 am

First and foremost, use a PHPAccelerator with plenty (128MB+ recommended) of RAM cache. And activate ViewCache (if you find pages getting cached incorrectly, tune their cache-blocks), TemplatCache, TemplatCompile.

I get cached page load times of below 0.15s with those settings on a 3GHz P4 (Linux or FreeBSD).

Visit http://triligon.org

Saturday 17 December 2005 10:58:35 am

Hi Denis,

This is good topic ;)

If possible use $node.children array if you need access to children or $node.parent if you need access to parent object. If you will reduce count of fetches this can give you some additional performance gain. Write proper code without notices, warnings, use deboug output for development. If you can do something on 2 same ways, check which one is faster.

For better performance, you can replace complex template code with custom operators that do the same in PHP code. For example instead of fetching whole objects for creating dropdown list use custom tpl operator which returns SQL array. Much faster ...

Use {cache-block} for optimization your pagelayout. If possible, use static cache, this will give you really good performance.

For the best performance, use Linux and MySQL.

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Saturday 17 December 2005 3:00:33 pm

While for political reasons I'm currently developping againt Linux (both 2.4 and 2.6), on similar spec'ed hardware I've noticed little difference between FreeBSD 4.11 and Linux 2.6 (Linux 2.4 isn't quite as good). However, I don't use safemode (it's an ugly, misguided hack with little security value when you come down to it). I also think that FreeBSD DOES cache the stat results if it got enough RAM to do so, so it shouldn't be that expensive (writes on UFS1 can be expensive because of the drives usually being synced instantly). Furthermore, claiming Linux is invariably faster isn't of much use without stating the filesystem in question (I've found JFS to be dog slow, for one and I wouldnt touch reiser, ever).

I don't manage getting much below 0.1s (nowhere close to 0.05s, anyway) on 3GHz P4/Athlon64 on either though. FWIW, there's a lot of variables involved. If you don't get below 0.5s something's likely wrong and might be tunable with proper cache settings/PHP setups, but if you dont get 0.1s over 0.2s it could mean your setup still is near it's peak.

I would love to see some formal benchmarks (especially once you get into big to huge sites with hundreds of thousand of nodes [1]) on different OSs

[1] Below that, throwing more hardware at it will let it scale pretty well to handle more users, but I'm not too sure what would happen with millions of nodes.

Visit http://triligon.org

Tuesday 20 December 2005 2:15:53 am

We need to agree on the variables involved with optimisation. I've knocked up a small list
which should be expanded.

Hardware
--------

CPU         : 
Memory      :
Disk space  :

Sofware
-------
OS               :
SQL             :
WebServer    :
PHP             :
Accelerator   :
eZ Version    :

eZ
--

Site.ini

[ContentSettings]
ViewCaching=enabled
PreViewCache=enabled

[TemplateSettings]
NodeTreeCaching=enabled
TemplateCache=enabled
TemplateCompile=enabled
TemplateCompression=enabled
TemplateOptimization=enabled

[SearchSettings]
DelayedIndexing=enabled

We also need to have several aims. Most of the site.ini settings here will boost speed *after* cache has been created. But, for example, DelayedIndexing helps to speed up the publishing process.

So, some priorities:

1. Browsing site.
2. Publishing.
3. Building cache after clearing.

Please add to this.

Paul

Thursday 12 January 2006 9:19:01 am

Some basic performance notes from the requirements page at http://ez.no/products/ez_publish_cms/info/requirements_for_ez_publish :

- For the best performance, we recommend using Linux and Mysql. Some other factors that may influence the performance of your site are:
- The number of page views per unit time.
- The number of concurrent users.
- The number of nodes. This can affect search and navigation speed when you have several hundred thousand nodes.
- Update frequency, e.g. how often your content is changed.
- The complexity of your templates. (For better performance, you could replace complex pieces of template code with custom operators that do the same in PHP code.)

I still do not loose hope this thread will revive and eventually form a doc :)

NXC - OPEN RELIABLE

Thursday 19 January 2006 4:20:09 am

Paul Forsyths suggestion to do:

Site.ini

[ContentSettings]
ViewCaching=enabled
PreViewCache=enabled

[TemplateSettings]
TemplateCache=enabled
TemplateCompile=enabled
TemplateCompression=enabled
TemplateOptimization=enabled

[SearchSettings]
DelayedIndexing=enabled

Unfortunately these settings messed up my whole site. Images and text disappeared and now, after removing those settings I cannot get the images back...

Edit: After manually handling the cache I now have everything back :) But why did stuff disappear from those settings?

Edit 2: It seems caching removes $node from my pagelayout.tpl. So in order to make use of caching I need to find a way to access these values in the pagelayout without touching $node:

$node.path_identification_string
$node.name
$node.url_alias

Thursday 19 January 2006 6:04:30 am

Hi all,
Would UsePersistentConnection=enabled gain some more speed? Documentation says something about unwanted effects in the past. Is that information still relevant?

http://ez.no/doc/ez_publish/technical_manual/3_6/reference/configuration_files/site_ini/databasesettings/usepersistentconnection

http://www.netgen.hr/eng

Thursday 19 January 2006 9:58:11 am

Some performance metrix definitions can be found in this whitepaper http://ez.no/content/download/95639/383244/file/Whitepaper+Scalability+and+Performance.pdf with a reference to http://ez.no/community/articles/clustering_ez_publish where cluster environment is described as yet another option to speed up your system.

NXC - OPEN RELIABLE

Thursday 02 February 2006 2:31:59 am

Comments for an speed boost and lowering number of fetches / sql quries from http://ez.no/doc/ez_publish/technical_manual/3_6/templates/information_extraction/outputting_node_and_object_data#comment2472

If you need to display some information about the children or grand children in the node template this is possible with $node.children and $node.children.0.children (if any children exist this will loop thru any children of your first child)
To loop thru children:

{foreach $node.children as $nodechild}
  {$nodechild.url_alias|ezurl}
  {$nodechild.name}
  {$nodechild.node_id}
{/foreach}

The same thing can be done with parents: $node.parent

Remember to only use $node in node templates and not in your pagelayout file.
Because it's not available on cached pages (ViewCaching).

NXC - OPEN RELIABLE

Monday 06 March 2006 7:51:09 am

If eZ is used as the home page, you can preprocess it - which just converts it into an HTML image.

That will allow you to have a faster home page.

There is an article at Dr. Dobb's Journal http://www.ddj.com/documents/s=9938/ddj0601g/0601g.html, and supporting code at http://wirehopper.com/php/preprocess.php.

I have used this general approach on some very high traffic homepages, with great success.

In addition, I used cache-blocks, and for very high speed content delivery, created specialized templates that had only enough code to deliver the content (single streamlined CSS, very limited HTML).

Another approach is to use eZ to create PHP that can deliver the content dynamically (this works well when the content is a component of another page).