Benchmarking eZ: memory consumption for the webservice use case

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

Introduction

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

6 replies

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: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye
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 ;) Cheers Paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
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. JL. http://www.acidre.com
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 maxime.thomas@wascou.org \| www.wascou.org \| http://twitter.com/wascou Company Blog : http://www.wascou.org/eng/Company/Blog Technical Blog : http://share.ez.no/blogs/maxime-thomas
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!

eZ debug

Timing:	Jan 18 2025 02:52:54
Script start
Timing:	Jan 18 2025 02:52:54
Module start 'layout'
Timing:	Jan 18 2025 02:52:54
Module start 'content'
Timing:	Jan 18 2025 02:52:54
Module end 'content'
Timing:	Jan 18 2025 02:52:54
Script end

Main resources:

Total runtime	0.1618 sec
Peak memory usage	4,096.0000 KB
Database Queries	84

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0070	589.2969	152.6563
Module start 'layout'	0.0070	0.0031	741.9531	39.5156
Module start 'content'	0.0101	0.1502	781.4688	834.0625
Module end 'content'	0.1603	0.0015	1,615.5313	22.3984
Script end	0.1618		1,637.9297

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	2.0280	16	0.0002
Check MTime	0.0013	0.8204	16	0.0001
Mysql Total
Database connection	0.0016	1.0190	1	0.0016
Mysqli_queries	0.0840	51.9060	84	0.0010
Looping result	0.0007	0.4085	82	0.0000
Template Total	0.1339	82.7	2	0.0669
Template load	0.0025	1.5633	2	0.0013
Template processing	0.1314	81.1640	2	0.0657
Template load and register function	0.0001	0.0909	1	0.0001
states
state_id_array	0.0010	0.6283	2	0.0005
state_identifier_array	0.0011	0.7037	3	0.0004
Override
Cache load	0.0021	1.2967	34	0.0001
Sytem overhead
Fetch class attribute name	0.0012	0.7356	12	0.0001
Fetch class attribute can translate value	0.0004	0.2618	5	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0131	13	0.0000
XML
Image XML parsing	0.0023	1.4200	5	0.0005
General
dbfile	0.0014	0.8608	41	0.0000
String conversion	0.0000	0.0056	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	forum_topic/full.tpl	extension/community_design/design/suncana/override/templates/forum_topic/full.tpl
7	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
6	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 22 Number of unique templates used: 5

Time used to render debug report: 0.0002 secs