About memory_limit

Next topic

Author	Message
Pascal France	Tuesday 17 January 2006 6:27:36 am Hi, I met a PHP developper who don't anderstand (in fact, he can't believe) why eZP need such a bit size of memory (64Mo in official documentation). As I'm not a developper I didn't what to answer. Could you tell me the reason about this big memory_limit value ? I'm very concerned because I have to choice between professional shared or dedicated host. Is this solution: ini_set( "memory_limit", "-1M"); to the begining of index.php a good solution if I can't access php.ini ? Regards Pascal Ce qui embellit le désert c'est qu'il cache un puits... quelque part... (A. de Saint-Exupéry) - http://luxpopuli.fr/eZ-Publish
Frederik Holljen	Tuesday 17 January 2006 6:51:00 am There are two things that currently push the maximum memory used by eZ publish currently. None of them occur frequently in production usage: 1. Template compilation. When a template is changed it is compiled into php code. The compilation process currently needs to hold all templates (also included ones, a recursive process) in memory. In eZ components we we only compile one template at the time regardless of any includes. This reduces memory usage. 2. The conversion of language XML files into more convenient and cacheable php files. Similarly to 1. the current converter needs to have all of the XML file in memory. The language files have become quite large over time which means that a lot of memory is used. This issue is addressed in eZ components.

Author

Message

Tuesday 17 January 2006 6:27:36 am

Hi,

I met a PHP developper who don't anderstand (in fact, he can't believe) why eZP need such a bit size of memory (64Mo in official documentation).

As I'm not a developper I didn't what to answer.

Could you tell me the reason about this big memory_limit value ?

I'm very concerned because I have to choice between professional shared or dedicated host.

Is this solution:

ini_set( "memory_limit", "-1M");

to the begining of index.php a good solution if I can't access php.ini ?

Regards

Pascal

Ce qui embellit le désert c'est qu'il cache un puits... quelque part... (A. de Saint-Exupéry) - http://luxpopuli.fr/eZ-Publish

Frederik Holljen

Tuesday 17 January 2006 6:51:00 am

There are two things that currently push the maximum memory used by eZ publish currently. None of them occur frequently in production usage:
1. Template compilation. When a template is changed it is compiled into php code. The compilation process currently needs to hold all templates (also included ones, a recursive process) in memory. In eZ components we we only compile one template at the time regardless of any includes. This reduces memory usage.
2. The conversion of language XML files into more convenient and cacheable php files. Similarly to 1. the current converter needs to have all of the XML file in memory. The language files have become quite large over time which means that a lot of memory is used. This issue is addressed in eZ components.

eZ debug

Timing:	Jan 31 2025 00:37:47
Script start
Timing:	Jan 31 2025 00:37:47
Module start 'layout'
Timing:	Jan 31 2025 00:37:47
Module start 'content'
Timing:	Jan 31 2025 00:37:47
Module end 'content'
Timing:	Jan 31 2025 00:37:47
Script end

Main resources:

Total runtime	0.0253 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0046	588.0156	151.1953
Module start 'layout'	0.0046	0.0034	739.2109	220.6719
Module start 'content'	0.0080	0.0154	959.8828	997.8984
Module end 'content'	0.0234	0.0019	1,957.7813	29.9922
Script end	0.0253		1,987.7734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	10.8262	14	0.0002
Check MTime	0.0011	4.3659	14	0.0001
Mysql Total
Database connection	0.0008	3.0433	1	0.0008
Mysqli_queries	0.0019	7.3753	3	0.0006
Looping result	0.0000	0.0358	1	0.0000
Template Total	0.0014	5.4	1	0.0014
Template load	0.0011	4.2124	1	0.0011
Template processing	0.0003	1.1804	1	0.0003
Override
Cache load	0.0007	2.7393	1	0.0007
General
dbfile	0.0020	7.7594	8	0.0002
String conversion	0.0000	0.0282	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs