not enough memory using webhotel

Next topic

Author	Message
Lars Sønderby	Sunday 04 April 2004 12:43:50 am Hi everyone, I have tried to install eZ 3.3-3 on my webhotel (a standard cheap $2 a month webhotel). But I get this memory error message : <b> Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 184320 bytes) in /customers/xxxxxx.dk/xxxxxxx.dk/httpd.www/xxxxxxx/kernel/classes/ezpackage.php on line 2140 Fatal error: eZ publish did not finish it's request The execution of eZ publish was abruptly ended, the debug output is present below. </b> Doing a infophp() I can see that I have memory limit of 8 mb (memory_limit 8M). As far as I can see there is no way of changing that or am I wrong? I have looked around the forum to see if i'm the only one encountering this problem. And I am not. http://www.ez.no/index.php/community/forum/install_configuration/installation_on_commercial_webspace_providers But I still can't find a tread that actually gives a solution to the problem. Does the memory limit (which I am sure a lot of people are encountering) mean that I cannot use Ez systems at all? What can I do?
Tony Wood	Sunday 04 April 2004 2:41:03 pm Hi, You could try contacting the eZ publosh hosting partners. They know about eZ publish and ensure their hosting environments work with eZ publish. http://www.ez.no/index.php/services/hosting If these are not able to help you, it appears that eZ publish 3.4 (due out the summer) will be below 8m in size and should hopefully solve some of the hosting problems. --tony Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Author

Message

Sunday 04 April 2004 12:43:50 am

Hi everyone,

I have tried to install eZ 3.3-3 on my webhotel (a standard cheap $2 a month webhotel). But I get this memory error message :

<b>

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 184320 bytes) in /customers/xxxxxx.dk/xxxxxxx.dk/httpd.www/xxxxxxx/kernel/classes/ezpackage.php on line 2140
Fatal error: eZ publish did not finish it's request

The execution of eZ publish was abruptly ended, the debug output is present below.

</b>

Doing a infophp() I can see that I have memory limit of 8 mb (memory_limit 8M). As far as I can see there is no way of changing that or am I wrong?

I have looked around the forum to see if i'm the only one encountering this problem. And I am not.
http://www.ez.no/index.php/community/forum/install_configuration/installation_on_commercial_webspace_providers

But I still can't find a tread that actually gives a solution to the problem. Does the memory limit (which I am sure a lot of people are encountering) mean that I cannot use Ez systems at all?

What can I do?

Tony Wood

Sunday 04 April 2004 2:41:03 pm

Hi,

You could try contacting the eZ publosh hosting partners. They know about eZ publish and ensure their hosting environments work with eZ publish.
http://www.ez.no/index.php/services/hosting

If these are not able to help you, it appears that eZ publish 3.4 (due out the summer) will be below 8m in size and should hopefully solve some of the hosting problems.

--tony

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

eZ debug

Timing:	Jan 19 2025 09:54:34
Script start
Timing:	Jan 19 2025 09:54:34
Module start 'layout'
Timing:	Jan 19 2025 09:54:34
Module start 'content'
Timing:	Jan 19 2025 09:54:36
Module end 'content'
Timing:	Jan 19 2025 09:54:36
Script end

Main resources:

Total runtime	1.1552 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.0070	589.2813	152.6406
Module start 'layout'	0.0070	0.0031	741.9219	39.4766
Module start 'content'	0.0100	1.1437	781.3984	528.5391
Module end 'content'	1.1537	0.0014	1,309.9375	8.1406
Script end	1.1551		1,318.0781

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.2832	16	0.0002
Check MTime	0.0014	0.1194	16	0.0001
Mysql Total
Database connection	0.0008	0.0667	1	0.0008
Mysqli_queries	1.0988	95.1228	54	0.0203
Looping result	0.0008	0.0654	52	0.0000
Template Total	1.1154	96.6	2	0.5577
Template load	0.0021	0.1835	2	0.0011
Template processing	1.1132	96.3696	2	0.5566
Template load and register function	0.0002	0.0196	1	0.0002
states
state_id_array	0.0013	0.1136	1	0.0013
state_identifier_array	0.0023	0.1953	2	0.0011
Override
Cache load	0.0017	0.1484	22	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0542	2	0.0003
Fetch class attribute name	0.0011	0.0946	3	0.0004
XML
Image XML parsing	0.0043	0.3755	2	0.0022
class_abstraction
Instantiating content class attribute	0.0000	0.0008	3	0.0000
General
dbfile	0.0067	0.5827	16	0.0004
String conversion	0.0000	0.0008	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
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	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: 13 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs