Looking for answers - Will EZPublish withstand the load?

Author Message

Damian S

Monday 03 October 2005 5:29:44 pm

We want to create an ethnic internet portal similar to Yahoo or MSN but much less complex. We are open to any type of open source product and/or paid components-modules.

I am talking about following features:

- E-mail accounts to public
- Dating/matching services
- Real estate services
- Car dealership services
- Blog
- Forum
- Chat
- Auctions
- Online articles, type of an online magazine
- Directories - categories, subcategories, sub-sub categories for companies (such as Yahoo Company Directories)
- Classifieds
- E-commerce - we want to be selling products such as t-shirts, mugs, pens, etc. with our logo
- Banners, advertising management with reports and tracking
- SMS services

The platfrom must have the ability to be fully customizable in the front-end area (website look and layout) so we can create a well layed out site with great graphics. We can not accept the looks of most of the portal sites we have seen built based on the open source platforms. I do not understand if that is caused by the limitation of the plaftorms or by simply people not caring about the look of the sites. Please explain.

Which platform would be suitable, the most flexible, stable and expandable for this type of project?

Please list them or at least point me in the right direction.

Thank you very much.

Frederik Holljen

Tuesday 04 October 2005 12:04:41 am

Hi,

It's not easy to answer a simpel yes or no on your main question (will it withstand the load) since it depends on a number of factors:
- how many (simultaneous) editors
- how many edits per day
- how many (roughly) articles/objects
- how much and what parts of the site can be shown statically
- how many hits per day
- what kind of hardware

For a portal of this kind my guess is that you will have large hardware resources but also very many hits. The rest of my comment takes this assumption.

eZ publish has a very flexible content object model that you can use to model various content classes such as a blog entry, an article a forum message etc. The content engine does not support an unlimited amount of objects though and you will (most probably) have a high content load. I would suggest to use the content engine for parts of your site and to write custom modules for the parts with the highest object load.
E.g: Content engine:
- e-commerce
- banners
- directories
- online articles etc.
- Real estate services

custom engine:
- blog
- forums
- chat
- etc.

Your requirements may change this list of course. For the custom modules you have two modules, you can take existing products and embed these into eZ publish or you can write them using the eZ publish libraries. Using existing products is probably faster (in implementation time) but gives you less flexibility since the data and the design from the third party product is in an "alien" format.
If you make the custom modules yourself you can build on the eZ publish libraries (most notably the persistent object, or the content object system itself) which will ease the development considerably. Also since you are using eZ publish directly it is much easier to facilitate built in functionality like the role system.

When it comes to design many low end open source CMS systems generate HTML in their code. This limits the design possibilities. The high end (like eZ publish) have all their HTML in templates which means that you can change the design exactly to your liking.

Hope this little introduction is helpful.

Cheers

Mikhail Chekanov

Tuesday 04 October 2005 2:15:44 am

Too complex for my english, sorry. I'll try in bulgarian (am i right - you are bulgarian?):

Po prinzip e vyzmozhno, no nyama da stane. eZ e tezhko prilozhenie, prekaleno golyamo natovarvane shte imate. Osven tova, taka ili inache shte imate neobhodimost da hackvate kernel, koeto vodi do mnogo seriozna rabota po podryzhka na reshenieto - v kraya na krayshtata ste imate svoya sistema, izgradena vyrhu eZ framework.
Sistemata mozhe da izdyrzhi takiva natovarvaniya, obache ne mnogo dobre se opravya pri ednovremenno redaktirane ot mnogo posetiteli. Edin obiknoven server nyama da izdyrzhi poveche ot 3-4 zaprosa/sec v takyv rezhim. Ot druga starana sistemata у mnogo gyvkava - mozhe da se pravi pochti vsichko.

Bachkam po takiva proekti ot godini, i za .bg po edno vreme, taka che gore-dolu predstavlyavam za kakvo mozhe da stane duma. Po-dobre da probvate framework po-nisko nivo - ot sorta na ruby on rails, ili neshto na php. To est 'ez publish' kato cms nyama stoynost za takyv proekt, obache mozhete da ispolzvate komponentite mu kato framework.

--
mike
#6595551

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 18 2025 20:54:35
Script start
Timing: Jan 18 2025 20:54:35
Module start 'layout'
Timing: Jan 18 2025 20:54:35
Module start 'content'
Timing: Jan 18 2025 20:54:37
Module end 'content'
Timing: Jan 18 2025 20:54:37
Script end

Main resources:

Total runtime1.1965 sec
Peak memory usage4,096.0000 KB
Database Queries59

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0061 588.0547152.6406
Module start 'layout' 0.00620.0027 740.695339.4766
Module start 'content' 0.00881.1863 780.1719585.6719
Module end 'content' 1.19510.0013 1,365.843812.1094
Script end 1.1964  1,377.9531 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00320.2676160.0002
Check MTime0.00130.1084160.0001
Mysql Total
Database connection0.00100.087210.0010
Mysqli_queries1.138795.1719590.0193
Looping result0.00060.0514570.0000
Template Total1.160997.020.5804
Template load0.00190.160520.0010
Template processing1.158996.863420.5795
Template load and register function0.00020.020210.0002
states
state_id_array0.00210.172510.0021
state_identifier_array0.00120.103720.0006
Override
Cache load0.00160.1379570.0000
Sytem overhead
Fetch class attribute can translate value0.00080.068630.0003
Fetch class attribute name0.00150.125540.0004
XML
Image XML parsing0.00080.065430.0003
class_abstraction
Instantiating content class attribute0.00000.000740.0000
General
dbfile0.00190.1575160.0001
String conversion0.00000.000740.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
3content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
10content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
7content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
1content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 23
 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs