Forums / Developer / caching / performance

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

caching / performance

Previous topic

Developer

Next topic

Author	Message
Georg Franz	Saturday 28 February 2004 7:41:40 am Hi, some thoughts about performance of ez: ez2 had a performance problem with doing a lot of queries (e.g. the getTree methods), but was very fast with template processing. At ez3, it's vice versa - the query amount was dramaticly reduced, but the template processing is very slow. Now the ez crew is working hard on the new "template compilation feature" which is very unstable at the moment. Next problem: The amount of cache-files. At my installation, "clearing the cache" is a big challenge for my server (clearing the cache completely lasts 60 up to 120 seconds) And after that, the challenge is even bigger: recreating the cache. And - if you have "luck" - two or more spiders crawls your site right at the moment you are clearing the cache and causes a lot of unique page views. So the you can't speak of "performance" anymore, "slowness" is the better word ;-) I've made some thoughts, one idea is: Why using cache-files? Why not using the database for caching (add one or more "cache-tables")? Has anybody of the ez crew tried this? Advantages: -) Reduces the "cache-files" to a minimum -) A better Cache-Handling is possible Kind regards, Emil. Best wishes, Georg. -- http://www.schicksal.com Horoskop website which uses eZ Publish since 2004
Björn X	Monday 01 March 2004 5:54:41 am Maybe it would be wise to layout your advantages a little more. I see some disadvantages -a php accelerator won't work with those cached file -you will notice a slow db server because of the many writes and reads to the db. -the db server will use more ram -hitting a single file on the disk is usually faster then selecting a row from the db
Georg Franz	Monday 01 March 2004 1:01:13 pm Hi Björn, yes - I know your points, but that's the theory. Has anyone tried it? At my installation, the "template load" takes 40% - 60% of the performance. The sql queries (there are 9) takes 0.01%. The big rest is "template processing" which should be better, if the template compilation feature is ready to use. If the ez cache is empty, around 300 queries takes 0.9% up to 1.5% of the total performance. You can't use a php-accellarator at a large installation for the ez cache files. (Too many files.) Kind regards, Emil. Best wishes, Georg. -- http://www.schicksal.com Horoskop website which uses eZ Publish since 2004

Author

Message

Georg Franz

Saturday 28 February 2004 7:41:40 am

Hi,

some thoughts about performance of ez:

ez2 had a performance problem with doing a lot of queries (e.g. the getTree methods), but was very fast with template processing.

At ez3, it's vice versa - the query amount was dramaticly reduced, but the template processing is very slow. Now the ez crew is working hard on the new "template compilation feature" which is very unstable at the moment.

Next problem: The amount of cache-files.

At my installation, "clearing the cache" is a big challenge for my server (clearing the cache completely lasts 60 up to 120 seconds)

And after that, the challenge is even bigger: recreating the cache.

And - if you have "luck" - two or more spiders crawls your site right at the moment you are clearing the cache and causes a lot of unique page views. So the you can't speak of "performance" anymore, "slowness" is the better word ;-)

I've made some thoughts, one idea is:

Why using cache-files? Why not using the database for caching (add one or more "cache-tables")? Has anybody of the ez crew tried this?

Advantages:
-) Reduces the "cache-files" to a minimum
-) A better Cache-Handling is possible

Kind regards,
Emil.

Best wishes,
Georg.

--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004

Björn X

Monday 01 March 2004 5:54:41 am

Maybe it would be wise to layout your advantages a little more.

I see some disadvantages

-a php accelerator won't work with those cached file
-you will notice a slow db server because of the many writes and reads to the db.
-the db server will use more ram
-hitting a single file on the disk is usually faster then selecting a row from the db

Georg Franz

Monday 01 March 2004 1:01:13 pm

Hi Björn,

yes - I know your points, but that's the theory. Has anyone tried it?

At my installation, the "template load" takes 40% - 60% of the performance.
The sql queries (there are 9) takes 0.01%.

The big rest is "template processing" which should be better, if the template compilation feature is ready to use.

If the ez cache is empty, around 300 queries takes 0.9% up to 1.5% of the total performance.

You can't use a php-accellarator at a large installation for the ez cache files. (Too many files.)

Kind regards,
Emil.

Best wishes,
Georg.

--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004