large datasets

Author Message

Dennis Jessen

Friday 09 March 2007 6:31:32 am

Hello

i have the oppertunity to use eZ publish to develop an webshop, the experience I have with eZ is from rather 'small content' sites.

at some point in time the webshop will contain around 2.5 million objects/products with possibly as much as 30 attributes. This is just the products.
On average i would think that 5 of these attributes would be empty / non-existant.

i havent had any experinces yet with datasets of this size, and wouldn't mind some input from those that have.

some questions i have, among many!

Should I use the contentobject model to store products, giving many rows of contentObject_attributes ( 25*2.5mil ) * 2.5mil contentObjects.

Would I be better of extending the persistentObject, and if I do, what could the possible drawbacks be ( caching etc ? ).

To start with we have a dedicated server with mysql and one dedicated webserver, and possibly we would use the ezDBcachehandler to prepare for more webservers.
would this be overkill and are there any issues like image fetching etc.

Obviously all this is something I just have to test to gain my own experinces, but nonetheless any input would be much appreciated.

grettings

Dennis

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 19 2025 03:30:54
Script start
Timing: Jan 19 2025 03:30:54
Module start 'layout'
Timing: Jan 19 2025 03:30:54
Module start 'content'
Timing: Jan 19 2025 03:30:56
Module end 'content'
Timing: Jan 19 2025 03:30:56
Script end

Main resources:

Total runtime1.8982 sec
Peak memory usage4,096.0000 KB
Database Queries46

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0058 589.0313152.6094
Module start 'layout' 0.00580.0035 741.640639.4297
Module start 'content' 0.00941.8871 781.0703402.6328
Module end 'content' 1.89650.0016 1,183.70318.1953
Script end 1.8981  1,191.8984 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00370.1932160.0002
Check MTime0.00130.0702160.0001
Mysql Total
Database connection0.00070.034810.0007
Mysqli_queries1.853597.6476460.0403
Looping result0.00050.0260440.0000
Template Total1.859097.920.9295
Template load0.00230.122820.0012
Template processing1.856797.813520.9283
Template load and register function0.00030.015710.0003
states
state_id_array0.00180.094410.0018
state_identifier_array0.00110.057920.0005
Override
Cache load0.00190.0981160.0001
Sytem overhead
Fetch class attribute can translate value0.00080.044710.0008
Fetch class attribute name0.00100.054310.0010
XML
Image XML parsing0.00050.024110.0005
class_abstraction
Instantiating content class attribute0.00000.000310.0000
General
dbfile0.00120.0607100.0001
String conversion0.00000.000540.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
1content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
3content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
2content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 8
 Number of unique templates used: 5

Time used to render debug report: 0.0003 secs