performance

«

Previous topic

|

|

Next topic

»

Author	Message
Francis Nart	Tuesday 09 December 2003 2:55:54 am I am brand new to ez publish and I wonder if it is able toi set up several site powered by ez publish on a single server. My question is : can we use ez publish on serveral sites a server (PiV, 2.4 Ghz, 256 Mb) ? Moreover, is it better to have one ez publish installation that manages all sites or (and we would prefer that !), one ez publish instance for each site ? What would be the performance of the system for exemple : 10 ez publish sites on that server ? Best regards ! Francis.
Alex Jones	Tuesday 09 December 2003 6:25:22 am Franics, how much traffic do you expect the sites to generate? eZ publish can handle 10 different sites, but your server may not be able to handle it if you have large amounts of traffic. One note, if at all possible add more RAM to your server, no matter which set up you choose. This will have a major impact on the performance of the sites. Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Francis Nart	Tuesday 09 December 2003 6:45:32 am well frankly not much but do you think it would be better to have 10 implementations of ez publish on the server or one ez publish for all sites ? we'd prefer the first option (in term of maintenance, it's much easier for us to separate accounts !). But to your opinion (this is a Linux/Apache/MySQL server), 512 or even better 1 Gb would be better ? By the way, thank you for your reply ! Francis.
Bård Farstad	Tuesday 09 December 2003 6:57:30 am In terms of performance it's faster to have one eZ publish installation running 10 sites. However if some of the sites have very special requirements this can be a problem. One eZ publish installation uses very much less memory than 10, even if it's running 10 sites. This is specially noticeable when you're using a PHP Accelerator (which is highly recommended). --bård Documentation: http://ez.no/doc
Alex Jones	Tuesday 09 December 2003 6:59:55 am Okay a couple of more questions... Are these sites related to eachother? Will they have any content in common? Personally, I would try to use a single install though it requires a good bit more planning as you need to ensure you set up the appropriate roles and separate content sections. But, it also means that you only have to install extensions and upgrades in one spot. Also, it can cut down on different logins/accounts for people who use more than one of the sites. As for RAM, upgrading to 512 megs should be a noticeable improvement. Then, you can watch the server's performance and decide if you need to bump it up to 1 gig. Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Bård Farstad	Tuesday 09 December 2003 7:02:20 am You can run the sites on the same eZ publish installation but with different database. This does not require that much planning but gives the speed/memory gain since you will have 1/10 the number of files which needs to be compiled and stored in memory. --bård Documentation: http://ez.no/doc
Francis Nart	Tuesday 09 December 2003 7:09:35 am ok i understand this ! the sites won't be related to each other but we currently run a dedicated server with an ensim interface (that gives us the possibility to manage the account of our clients). setting up ez publish for the whole server would be beyond our network and server knowledge...but your explanation on memory use especially for caching templates is quite relevant ! We count on a maximum of 200 users a day on each site which is not much but with 10 installations (I mean 10 ez publish) it might be too much for our server even with 512 Mb !

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 04:25:02
Script start
Timing:	Jan 31 2025 04:25:02
Module start 'layout'
Timing:	Jan 31 2025 04:25:02
Module start 'content'
Timing:	Jan 31 2025 04:25:02
Module end 'content'
Timing:	Jan 31 2025 04:25:02
Script end

Main resources:

Total runtime	0.0133 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.0049	588.0000	151.1953
Module start 'layout'	0.0049	0.0024	739.1953	36.6016
Module start 'content'	0.0073	0.0048	775.7969	97.9844
Module end 'content'	0.0121	0.0012	873.7813	37.9922
Script end	0.0133		911.7734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	17.1570	14	0.0002
Check MTime	0.0010	7.4924	14	0.0001
Mysql Total
Database connection	0.0008	5.8575	1	0.0008
Mysqli_queries	0.0022	16.5464	3	0.0007
Looping result	0.0000	0.0752	1	0.0000
Template Total	0.0009	7.0	1	0.0009
Template load	0.0007	5.1519	1	0.0007
Template processing	0.0002	1.7800	1	0.0002
Override
Cache load	0.0005	3.6889	1	0.0005
General
dbfile	0.0009	6.7887	8	0.0001
String conversion	0.0000	0.0376	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