Forums / Discussions / Benchmarking eZ: memory consumption for the webservice use case

Tuesday 01 March 2011 6:16:01 am - 6 replies


The amount of memory used by the application to render a single page is an important metric to be taken into account when sizing webservers to cope with the desired amount of traffic. In this installment, we explore memory usage by eZ Publish, in the context of a "webservice" page, ie. a page rendering a very simple piece of text in json format. We focus on an aspect outside control of the developer: php files with class definitions.

» Read full blog post

Author Message

Nicolas Pastorino

Tuesday 01 March 2011 7:26:07 am

Nice post Gaetano.

It appears contribution to eZ Publish Community Project will leave some room for performance wizards to apply their magic !

Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter:

t :
G+ :

Paul Borgermans

Tuesday 01 March 2011 12:50:31 pm

Interesting Gaetano

On the memory allocation rules: I would add another one: plenty of RAM to cache file system access (var/cache + 500MB OS).

On the refactoring: rather a kernel rewrite as I am advocating for years now ;)



eZ Publish, eZ Find, Solr expert consulting and training

Gaetano Giunta

Wednesday 02 March 2011 12:33:17 am

@Paul thanks. I agree that a kernel rewrite is the way to go, iff it actually happens. Holding off incremental improvements for a year or even longer and then getting no new version at all is just frustrating...

Principal Consultant International Business
Member of the Community Project Board

Jean-Luc Nguyen

Thursday 03 March 2011 5:56:44 am

Very interesting article!

I used to automatically include autoload.php, but also found out that it used a lot of memory than including only really used PHP classes. It seems like a simple optimization, but it is actually more than necessary.


Maxime Thomas

Monday 14 March 2011 10:24:22 am

I agree on the debug part, it could be improved.

My 2 cents : I would like to see a kind of a main debug handler that will called and will run the different debug handlers.

For example, I need a different debug depending on used device : mobile or web.

Today, it's a kind of mess to have something coherent by overriding the kernel.

It could also be a good opportunity to try new ways of debug (plugin for browsers, headers for FirePHP, etc...)

Did I send you the data I've collected ??? Can't remember.

Maxime Thomas | |

Company Blog :
Technical Blog :

Gaetano Giunta

Monday 14 March 2011 12:23:37 pm

@maxime fully agree on everything about debug. No, did not get any data

Principal Consultant International Business
Member of the Community Project Board

You must be logged in to post messages in this topic!