Is it possible to handle 250.000.000 pages served / month

Next topic

Author	Message
Carlos Sschez	Monday 10 November 2008 9:01:59 am Firs of all, hi to everyone. I don't really know if this one is the right place to make such question but if i'm wrong tell me plase. I'm thinking about to install ezpublish product for a multimedia portal, and i would like to know (if anyone knows) if ezpublish is able to dispatch 250.000.000 pages monthly. And if there's something to take care about. For the hardware part there's no problem. And for the network bandwith there will be no problem also. So my question is if the data model or anything has any limitation. I can give you more data if you need. And any answer is greatly appreciated. Regards.
John Moritz	Tuesday 11 November 2008 5:22:40 am As far as i know, this will be no Problem because you can run ezPublish in cluster mode: http://ez.no/doc/ez_publish/technical_manual/4_0/features/clustering So the limitation is on your hardware. more servers = more pages u can serve/month
Carlos Revillo	Tuesday 11 November 2008 5:39:14 am Those pages shows ho to setup a ez cluster usign database for everything (caches, media files...), but this will increase the database load. It's also possible to use a NAS for this. I think it should be good to add some doc at the ez website, for setting a cluster in the other way. (using NAS or something)
André R.	Tuesday 11 November 2008 5:54:12 am If money is not a issue then I would recommend a SAN setup, scales a lot better then NAS because eZ Publish uses the files system quite heavy(4.1 will improve the situation a bit, but SAN is still superior to NAS). I have seen numbers from 80- 140 (local disk) 120 - 180 (SAN) req/second pr server, so this should be possible. But since a webpage contains more then just the html (images, javascript, css, video), you should use a reverse proxy like Varnish in front independent on how you choos to setup eZ Publish to lighten the load on the backend server(s) and be able to have a decent headroom to scale on. 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
Ole Morten Halvorsen	Tuesday 11 November 2008 6:50:11 am Another important aspect is how the traffic is distributed during the month / day. You need to plan to have capacity for the peaks, not the average. If 250.000.000 is the average per month (about 96 req/sec) you could have twice or even three times the amount of traffic during day time, but this depends on the type of site you have. Senior Software Engineer - Vision with Technology http://www.visionwt.com http://www.omh.cc http://www.twitter.com/omh eZ Certified Developer http://ez.no/certification/verify/358441 http://ez.no/certification/verify/272578

eZ debug

Timing:	Jan 19 2025 00:35:45
Script start
Timing:	Jan 19 2025 00:35:45
Module start 'layout'
Timing:	Jan 19 2025 00:35:45
Module start 'content'
Timing:	Jan 19 2025 00:35:46
Module end 'content'
Timing:	Jan 19 2025 00:35:46
Script end

Main resources:

Total runtime	0.6620 sec
Peak memory usage	4,096.0000 KB
Database Queries	69

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	589.2500	152.6406
Module start 'layout'	0.0052	0.0029	741.8906	39.4766
Module start 'content'	0.0081	0.6525	781.3672	664.4219
Module end 'content'	0.6606	0.0014	1,445.7891	12.1094
Script end	0.6620		1,457.8984

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.5198	16	0.0002
Check MTime	0.0017	0.2524	16	0.0001
Mysql Total
Database connection	0.0008	0.1234	1	0.0008
Mysqli_queries	0.6071	91.7054	69	0.0088
Looping result	0.0008	0.1231	67	0.0000
Template Total	0.6179	93.3	2	0.3090
Template load	0.0023	0.3419	2	0.0011
Template processing	0.6157	93.0004	2	0.3078
Template load and register function	0.0001	0.0218	1	0.0001
states
state_id_array	0.0019	0.2860	1	0.0019
state_identifier_array	0.0024	0.3678	2	0.0012
Override
Cache load	0.0019	0.2840	23	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0008	0.1152	5	0.0002
Fetch class attribute name	0.0013	0.2012	6	0.0002
XML
Image XML parsing	0.0010	0.1534	5	0.0002
class_abstraction
Instantiating content class attribute	0.0000	0.0018	6	0.0000
General
dbfile	0.0018	0.2775	17	0.0001
String conversion	0.0000	0.0013	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
5	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	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: 20 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs