Extremely slow after migration

Previous topic

Install & configuration

Next topic

Author	Message
Halvor M	Sunday 18 February 2007 12:56:56 am I just migrated my site to Domeneshop (www.domeneshop.no), running on a php4.4 server. The site works, but has now become extreeeemely slow: www.jusnytt.no Is this simply due to large resource drain from EZ, or is this something that would be fixable with some smart configuration changes? (The site was running fine on my beefed-up comp running wampserver).
Claudia Kosny	Sunday 18 February 2007 8:41:35 am Hi Halvor First of all check whether your cache directory is writable. If you have created/uploaded the directories via ftp, PHP might not be allowed to write into the var directory. So check the permissions of the var and all subdirectories. If that does not help enable the debug output as this will show you a list with some timing points on the bottom of each page. Maybe this will tell you where the time is spent. Concerning your webpage: The link for Halvor Manshaus does not lead to a valid page. Also you should run the page though the validator, there are some minor errors in the html. Apart from that it looks quite nice (can't say anything about the content as I don't speak Norwegian at all). Good luck Claudia

Author

Message

Halvor M

Sunday 18 February 2007 12:56:56 am

I just migrated my site to Domeneshop (www.domeneshop.no), running on a php4.4 server.

The site works, but has now become extreeeemely slow: www.jusnytt.no

Is this simply due to large resource drain from EZ, or is this something that would be fixable with some smart configuration changes? (The site was running fine on my beefed-up comp running wampserver).

Claudia Kosny

Sunday 18 February 2007 8:41:35 am

Hi Halvor

First of all check whether your cache directory is writable. If you have created/uploaded the directories via ftp, PHP might not be allowed to write into the var directory. So check the permissions of the var and all subdirectories.

If that does not help enable the debug output as this will show you a list with some timing points on the bottom of each page. Maybe this will tell you where the time is spent.

Concerning your webpage: The link for Halvor Manshaus does not lead to a valid page. Also you should run the page though the validator, there are some minor errors in the html. Apart from that it looks quite nice (can't say anything about the content as I don't speak Norwegian at all).

Good luck

Claudia

eZ debug

Timing:	Jan 31 2025 01:34:38
Script start
Timing:	Jan 31 2025 01:34:38
Module start 'layout'
Timing:	Jan 31 2025 01:34:38
Module start 'content'
Timing:	Jan 31 2025 01:34:38
Module end 'content'
Timing:	Jan 31 2025 01:34:38
Script end

Main resources:

Total runtime	0.0406 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0110	588.2500	151.2266
Module start 'layout'	0.0110	0.0051	739.4766	220.7188
Module start 'content'	0.0161	0.0227	960.1953	997.6172
Module end 'content'	0.0388	0.0017	1,957.8125	29.9922
Script end	0.0405		1,987.8047

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	8.5910	14	0.0002
Check MTime	0.0012	3.0067	14	0.0001
Mysql Total
Database connection	0.0040	9.8381	1	0.0040
Mysqli_queries	0.0031	7.6783	3	0.0010
Looping result	0.0000	0.0341	1	0.0000
Template Total	0.0012	3.0	1	0.0012
Template load	0.0010	2.5142	1	0.0010
Template processing	0.0002	0.4414	1	0.0002
Override
Cache load	0.0008	1.8659	1	0.0008
General
dbfile	0.0003	0.7417	8	0.0000
String conversion	0.0000	0.0223	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