Memory problem

Next topic

Author	Message
Michele Mader	Wednesday 26 February 2003 6:12:45 am I have installed ez3 without problems, but now i obtain the following error messages. Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 184320 bytes) in /home/mmader/ez3/var/cache/template/tree/a4518fa0d725fdd6e700a4821e382ea0.php on line 514 Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 12 bytes) in /home/mmader/ez3/lib/ezutils/classes/ezexecution.php on line 157 Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 32 bytes) in Unknown on line 0 I could set an higher value in php.ini, but i think it's a bad idea. Is eZ publish 3 really so heavy to run or there is some alternative solution?
Anders Jensen-Urstad	Wednesday 26 February 2003 7:07:58 am > I have installed ez3 without problems, but now i obtain the > following error messages. > > Fatal error: Allowed memory size of 8388608 bytes exhausted > (tried to allocate 184320 bytes) in > /home/mmader/ez3/var/cache/template/tree/a4518fa0d725fdd6e700a4821e382ea0.php > on line 514 > > Fatal error: Allowed memory size of 8388608 bytes exhausted > (tried to allocate 12 bytes) in > /home/mmader/ez3/lib/ezutils/classes/ezexecution.php on line > 157 > > Fatal error: Allowed memory size of 8388608 bytes exhausted > (tried to allocate 32 bytes) in Unknown on line 0 > > I could set an higher value in php.ini, but i think it's a > bad idea. > Is eZ publish 3 really so heavy to run or there is some > alternative solution? Well, the default 8MB isn't always sufficient. From http://ezwiki.blanko.info/index.php/3XPS_OutOfMemory : "On some configurations, eZ publish 3 needs more than 8Mb internal memory. Just raise the memorylimit for php (php_admin_value memory_limit 10M in (virtual) server config)"

Author

Message

Wednesday 26 February 2003 6:12:45 am

I have installed ez3 without problems, but now i obtain the following error messages.

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 184320 bytes) in /home/mmader/ez3/var/cache/template/tree/a4518fa0d725fdd6e700a4821e382ea0.php on line 514

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 12 bytes) in /home/mmader/ez3/lib/ezutils/classes/ezexecution.php on line 157

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 32 bytes) in Unknown on line 0

I could set an higher value in php.ini, but i think it's a bad idea.
Is eZ publish 3 really so heavy to run or there is some alternative solution?

Anders Jensen-Urstad

Wednesday 26 February 2003 7:07:58 am

> I have installed ez3 without problems, but now i obtain the
> following error messages.
>
> Fatal error: Allowed memory size of 8388608 bytes exhausted
> (tried to allocate 184320 bytes) in
> /home/mmader/ez3/var/cache/template/tree/a4518fa0d725fdd6e700a4821e382ea0.php
> on line 514
>
> Fatal error: Allowed memory size of 8388608 bytes exhausted
> (tried to allocate 12 bytes) in
> /home/mmader/ez3/lib/ezutils/classes/ezexecution.php on line
> 157
>
> Fatal error: Allowed memory size of 8388608 bytes exhausted
> (tried to allocate 32 bytes) in Unknown on line 0
>
> I could set an higher value in php.ini, but i think it's a
> bad idea.
> Is eZ publish 3 really so heavy to run or there is some
> alternative solution?

Well, the default 8MB isn't always sufficient. From http://ezwiki.blanko.info/index.php/3XPS_OutOfMemory :

"On some configurations, eZ publish 3 needs more than 8Mb internal memory. Just raise the memorylimit for php (php_admin_value memory_limit 10M in (virtual) server config)"

eZ debug

Timing:	Jan 18 2025 11:08:13
Script start
Timing:	Jan 18 2025 11:08:13
Module start 'layout'
Timing:	Jan 18 2025 11:08:13
Module start 'content'
Timing:	Jan 18 2025 11:08:13
Module end 'content'
Timing:	Jan 18 2025 11:08:13
Script end

Main resources:

Total runtime	0.6488 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0059	587.9063	152.6250
Module start 'layout'	0.0059	0.0032	740.5313	39.4453
Module start 'content'	0.0091	0.6381	779.9766	461.3828
Module end 'content'	0.6473	0.0015	1,241.3594	8.3359
Script end	0.6487		1,249.6953

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.5289	16	0.0002
Check MTime	0.0013	0.2072	16	0.0001
Mysql Total
Database connection	0.0008	0.1301	1	0.0008
Mysqli_queries	0.6050	93.2476	54	0.0112
Looping result	0.0005	0.0718	52	0.0000
Template Total	0.6177	95.2	2	0.3088
Template load	0.0023	0.3543	2	0.0011
Template processing	0.6154	94.8540	2	0.3077
Template load and register function	0.0002	0.0371	1	0.0002
states
state_id_array	0.0008	0.1273	1	0.0008
state_identifier_array	0.0012	0.1897	2	0.0006
Override
Cache load	0.0020	0.3015	32	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1033	2	0.0003
Fetch class attribute name	0.0009	0.1378	2	0.0004
XML
Image XML parsing	0.0002	0.0373	2	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0006	2	0.0000
General
dbfile	0.0007	0.1085	10	0.0001
String conversion	0.0000	0.0015	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	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 9 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs