Siteaccess Limit?

«

Previous topic

|

|

Next topic

»

Author	Message
Mahesh Arvind	Thursday 17 June 2004 7:19:12 am Is there any limit to the number of siteaccess that can be created with an instance of EZ Publish? Thanks Mahesh Thanks & Regards Mahesh
Kåre Køhler Høvik	Friday 18 June 2004 9:12:12 am No, there is no limit on the number of siteaccesses. The limiting factior would be performance issues. Kåre Høvik
steve walker	Monday 21 June 2004 3:26:18 am Ez Crew, Can you give any rough 'rule of thumb' comments about multiple site hosting? Are there any ramifications due to multiple cache copies? Or is the only factor the site hit rate? Does refreshing the cache on one site cause slow downs on the others? Any insights you have would be most welcome. Thanks, Steve. http://www.oneworldmarket.co.uk
steve walker	Wednesday 23 June 2004 2:44:15 am EzCrew, Would be great to see some information released on this... To re-word the information that I (and I think others) would find helpful... Lets take a server that has the ability to run 200 conventially setup PHP websites. Now, in this instance, what is the difference between having 200 seperate installations of EzPublish running one site each, and 1 installation of EzPublish running 200 sites? - Is the PHP memeory allocation the only issue here? Is there a rule of thumb that says "for a hit rate of x pages per hour you typically need a PHP memory allocation of y" - does work performed on one site affect the performance of other sites? Caching bleedover effects etc... An insight into where the stresses and strains lie within the system would be great. Are there any statistics you could provide, any live installations like "we have a server with x spec running y multiple sites off a single install"...? Any info appreciated. Regards, Steve. http://www.oneworldmarket.co.uk

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 31 2025 06:16:56
Script start
Timing:	Jan 31 2025 06:16:56
Module start 'layout'
Timing:	Jan 31 2025 06:16:56
Module start 'content'
Timing:	Jan 31 2025 06:16:56
Module end 'content'
Timing:	Jan 31 2025 06:16:56
Script end

Main resources:

Total runtime	0.0120 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0043	588.0313	151.1953
Module start 'layout'	0.0043	0.0020	739.2266	36.6172
Module start 'content'	0.0063	0.0040	775.8438	94.1250
Module end 'content'	0.0103	0.0017	869.9688	33.9922
Script end	0.0119		903.9609

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0021	17.8445	14	0.0002
Check MTime	0.0010	8.1342	14	0.0001
Mysql Total
Database connection	0.0006	5.1454	1	0.0006
Mysqli_queries	0.0020	16.4578	3	0.0007
Looping result	0.0000	0.0758	1	0.0000
Template Total	0.0013	11.0	1	0.0013
Template load	0.0010	8.7367	1	0.0010
Template processing	0.0003	2.1926	1	0.0003
Override
Cache load	0.0006	4.6945	1	0.0006
General
dbfile	0.0002	1.7577	8	0.0000
String conversion	0.0000	0.0419	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