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.