What PHP Accelerator do eZ use?

Next topic

Author	Message
Tony Wood	Monday 04 August 2003 3:15:47 am What PHP Accelerator do the eZ team use? I have noticed that ion cube PHP Accelerator folds under pressure. It has done so on two servers. eZ fails with eZFatalError(). 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
Jeroen van Gorkum	Saturday 09 August 2003 9:22:26 am according to http://webtools.mozilla.org/web-sniffer/, they're using PHPA/1.3.3r2 for ez.no. (sorry if that was meant to be kept secret). jeroen.
Bård Farstad	Saturday 09 August 2003 12:09:57 pm We use PHP Accelerator. We've had little problems with it. The only problems I've noted is under development. If you change a base class, derived objects of this class will not be updated. --bård Documentation: http://ez.no/doc
Tony Wood	Monday 11 August 2003 1:12:43 am Thanks all. I have emailled ioncube and explained the problem, hopefully they can find a fix for me. 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
Tony Wood	Monday 11 August 2003 1:22:35 am Jeroen , Thanks for the Mozilla link, its a nice tool :) 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 18 2025 16:19:37
Script start
Timing:	Jan 18 2025 16:19:37
Module start 'layout'
Timing:	Jan 18 2025 16:19:37
Module start 'content'
Timing:	Jan 18 2025 16:19:37
Module end 'content'
Timing:	Jan 18 2025 16:19:37
Script end

Main resources:

Total runtime	0.8074 sec
Peak memory usage	4,096.0000 KB
Database Queries	65

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0050	589.1484	152.6406
Module start 'layout'	0.0050	0.0020	741.7891	39.4766
Module start 'content'	0.0070	0.7990	781.2656	596.9219
Module end 'content'	0.8060	0.0014	1,378.1875	16.1484
Script end	0.8074		1,394.3359

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.3903	16	0.0002
Check MTime	0.0013	0.1590	16	0.0001
Mysql Total
Database connection	0.0009	0.1074	1	0.0009
Mysqli_queries	0.7540	93.3821	65	0.0116
Looping result	0.0013	0.1601	63	0.0000
Template Total	0.7773	96.3	2	0.3886
Template load	0.0022	0.2754	2	0.0011
Template processing	0.7750	95.9879	2	0.3875
Template load and register function	0.0001	0.0093	1	0.0001
states
state_id_array	0.0016	0.1922	1	0.0016
state_identifier_array	0.0009	0.1071	2	0.0004
Override
Cache load	0.0019	0.2302	24	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0747	3	0.0002
Fetch class attribute name	0.0010	0.1243	7	0.0001
XML
Image XML parsing	0.0010	0.1241	3	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0021	9	0.0000
General
dbfile	0.0008	0.0947	23	0.0000
String conversion	0.0000	0.0007	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
4	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
5	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
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 16 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs