Massive Multi Site

Previous topic

Developer

Next topic

Author	Message
Björn Dieding@xrow.de	Thursday 19 February 2004 8:41:24 am This is more linux/php question. My plan is to build a eZ with 1000 or 2000 siteacceses. I am wondering now at how many siteaccess will I notice an imense loss of performance, because of the amount of directories inside either the settings/siteaccess or var/siteaccessname Does any body know the answer or even dares? :-) Thank you Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Bård Farstad	Friday 20 February 2004 2:03:49 am Interesting. The only thing which I can think of which will cause overhead here is that you need to enable all 1000 siteaccesses. This means that you will use some memory for these 1000 lines. But this overhead should be much smaller than having 1000 installations by far. Each site can share the same php code and this will be cached really well. Haven't tested though. It would be interesting to hear about some test results ( mabye create a script which generates these siteaccesses for a test first? ) --bård Documentation: http://ez.no/doc
Björn Dieding@xrow.de	Friday 20 February 2004 8:32:02 am The final solution could look like this... 1.) catch all request on one ip, because we do not want apache to blow up. 2.) use mod perl to provide a fast mapping from external/unkown hosts to a common internal one 3.) do the usual mod_rw stuff 4.) prodive a little kernel hack to dynamicly match against a internal uri :-) Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/

Author

Message

Björn Dieding@xrow.de

Thursday 19 February 2004 8:41:24 am

This is more linux/php question.

My plan is to build a eZ with 1000 or 2000 siteacceses.

I am wondering now at how many siteaccess will I notice an imense loss of performance, because of the amount of directories inside either the settings/siteaccess or var/siteaccessname

Does any body know the answer or even dares? :-)

Thank you

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Bård Farstad

Friday 20 February 2004 2:03:49 am

Interesting. The only thing which I can think of which will cause overhead here is that you need to enable all 1000 siteaccesses. This means that you will use some memory for these 1000 lines. But this overhead should be much smaller than having 1000 installations by far. Each site can share the same php code and this will be cached really well.

Haven't tested though. It would be interesting to hear about some test results ( mabye create a script which generates these siteaccesses for a test first? )

--bård

Documentation: http://ez.no/doc

Björn Dieding@xrow.de

Friday 20 February 2004 8:32:02 am

The final solution could look like this...

1.) catch all request on one ip, because we do not want apache to blow up.
2.) use mod perl to provide a fast mapping from external/unkown hosts to a common internal one
3.) do the usual mod_rw stuff
4.) prodive a little kernel hack to dynamicly match against a internal uri :-)

eZ debug

Timing:	Jan 18 2025 22:14:06
Script start
Timing:	Jan 18 2025 22:14:06
Module start 'layout'
Timing:	Jan 18 2025 22:14:06
Module start 'content'
Timing:	Jan 18 2025 22:14:07
Module end 'content'
Timing:	Jan 18 2025 22:14:07
Script end

Main resources:

Total runtime	0.6847 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0067	587.8047	152.6094
Module start 'layout'	0.0067	0.0035	740.4141	39.4297
Module start 'content'	0.0102	0.6730	779.8438	544.9141
Module end 'content'	0.6832	0.0015	1,324.7578	12.1875
Script end	0.6847		1,336.9453

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.4711	16	0.0002
Check MTime	0.0013	0.1898	16	0.0001
Mysql Total
Database connection	0.0014	0.2014	1	0.0014
Mysqli_queries	0.6292	91.8875	57	0.0110
Looping result	0.0006	0.0853	55	0.0000
Template Total	0.6512	95.1	2	0.3256
Template load	0.0026	0.3850	2	0.0013
Template processing	0.6485	94.7122	2	0.3243
Template load and register function	0.0001	0.0174	1	0.0001
states
state_id_array	0.0008	0.1195	1	0.0008
state_identifier_array	0.0010	0.1405	2	0.0005
Override
Cache load	0.0021	0.3129	21	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0008	0.1202	2	0.0004
Fetch class attribute name	0.0013	0.1875	5	0.0003
XML
Image XML parsing	0.0011	0.1617	2	0.0006
class_abstraction
Instantiating content class attribute	0.0000	0.0016	6	0.0000
General
dbfile	0.0017	0.2443	23	0.0001
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/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.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
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.0002 secs