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