Best Practice: many extensions, or one extension

Next topic

Author	Message
John Moritz	Tuesday 30 September 2008 4:22:20 am Hello, i just want to ask, if its better to make 5 extensions or better 1 extension which includes everything? Is there a speed loss when i integrate to much extensions?
André R.	Tuesday 30 September 2008 6:00:18 am To some degree there is a slight speed loss, but unless you use a slow filesystem (windows / mac / nfs) or a lot of extension(~20) you won't really notice it much. Some of the speed loss is fixed in 4.1 though, by introducing a setting to turn of modified time checking on ini files. eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Piotrek Karaś	Friday 17 October 2008 7:53:51 am Hi, Basically, when we aim at generic solutions, we try to isolate tool functionalities and this leads to many extensions. Otherwise, when we implement a one-time client-dedicated solution, this usually grows bigger within one extension folder. We have some implementations that have 20+ extensions. We haven't noticed any significant problems at this point, but that also much depends on site optimization and cache-layer. Also, the more dynamic content you have, the more important this issue I would expect to be. -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

Author

Message

Tuesday 30 September 2008 4:22:20 am

Hello,

i just want to ask, if its better to make 5 extensions or better 1 extension which includes everything?
Is there a speed loss when i integrate to much extensions?

André R.

Tuesday 30 September 2008 6:00:18 am

To some degree there is a slight speed loss, but unless you use a slow filesystem (windows / mac / nfs) or a lot of extension(~20) you won't really notice it much. Some of the speed loss is fixed in 4.1 though, by introducing a setting to turn of modified time checking on ini files.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Piotrek Karaś

Friday 17 October 2008 7:53:51 am

Hi,

Basically, when we aim at generic solutions, we try to isolate tool functionalities and this leads to many extensions. Otherwise, when we implement a one-time client-dedicated solution, this usually grows bigger within one extension folder.

We have some implementations that have 20+ extensions. We haven't noticed any significant problems at this point, but that also much depends on site optimization and cache-layer. Also, the more dynamic content you have, the more important this issue I would expect to be.

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

eZ debug

Timing:	Jan 18 2025 19:19:50
Script start
Timing:	Jan 18 2025 19:19:50
Module start 'layout'
Timing:	Jan 18 2025 19:19:50
Module start 'content'
Timing:	Jan 18 2025 19:19:51
Module end 'content'
Timing:	Jan 18 2025 19:19:51
Script end

Main resources:

Total runtime	1.0156 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0080	588.0469	152.6406
Module start 'layout'	0.0080	0.0026	740.6875	39.4766
Module start 'content'	0.0107	1.0036	780.1641	575.9766
Module end 'content'	1.0143	0.0013	1,356.1406	12.1250
Script end	1.0156		1,368.2656

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0031	0.3101	16	0.0002
Check MTime	0.0013	0.1301	16	0.0001
Mysql Total
Database connection	0.0017	0.1632	1	0.0017
Mysqli_queries	0.9600	94.5217	59	0.0163
Looping result	0.0007	0.0738	57	0.0000
Template Total	0.9771	96.2	2	0.4886
Template load	0.0019	0.1905	2	0.0010
Template processing	0.9752	96.0226	2	0.4876
Template load and register function	0.0002	0.0149	1	0.0002
states
state_id_array	0.0009	0.0856	1	0.0009
state_identifier_array	0.0015	0.1465	2	0.0007
Override
Cache load	0.0016	0.1536	14	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0015	0.1444	3	0.0005
Fetch class attribute name	0.0011	0.1046	5	0.0002
XML
Image XML parsing	0.0015	0.1501	3	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0008	5	0.0000
General
dbfile	0.0009	0.0875	24	0.0000
String conversion	0.0000	0.0009	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
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
2	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: 12 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs