Scalability with a LOT of content

Next topic

Author	Message
Gabriel Ambuehl	Saturday 13 November 2004 7:59:49 am How's 3.5 gonna work for sites with a few thousand, tens of thousands or even hundreds of thousands of objects? The particular project I'm concerned about won't be heavy load (very little traffic expected) but there will eventually be at least tens of thousands objects (including images, with say 20 attributes per object) in many categories. Am I in for a scalability nightmare or is this gonna work fine (a low end dedicated box will be used but I'd hate to have to go for dual or quad boxes, much less clustering)? How will the admin interface (especially the dynamic tree in 3.5) cope with it? Visit http://triligon.org
Frederik Holljen	Saturday 13 November 2004 8:07:09 am eZ publish currently scales to around 500.000 objects. We are running several projects with an object count close to this. The tree menu of course does not scale to that many objects (the amount of data alone would be far more than most connections can handle). Therefore it is configurable; you can configure what object types to display, the max depth to display and the maximum number of nodes.
Gabriel Ambuehl	Saturday 13 November 2004 8:09:55 am Thanks for your comment. Do the hardware needs climb noticeably for the same amount of traffic on large sites or will I mostly be fine with the same hardware for the same amount of traffic (we will try to pack DBs in RAM, of course)? Visit http://triligon.org

Author

Message

Saturday 13 November 2004 7:59:49 am

How's 3.5 gonna work for sites with a few thousand, tens of thousands or even hundreds of thousands of objects?

The particular project I'm concerned about won't be heavy load (very little traffic expected) but there will eventually be at least tens of thousands objects (including images, with say 20 attributes per object) in many categories.

Am I in for a scalability nightmare or is this gonna work fine (a low end dedicated box will be used but I'd hate to have to go for dual or quad boxes, much less clustering)?

How will the admin interface (especially the dynamic tree in 3.5) cope with it?

Visit http://triligon.org

Frederik Holljen

Saturday 13 November 2004 8:07:09 am

eZ publish currently scales to around 500.000 objects. We are running several projects with an object count close to this.

The tree menu of course does not scale to that many objects (the amount of data alone would be far more than most connections can handle). Therefore it is configurable; you can configure what object types to display, the max depth to display and the maximum number of nodes.

Gabriel Ambuehl

Saturday 13 November 2004 8:09:55 am

Thanks for your comment. Do the hardware needs climb noticeably for the same amount of traffic on large sites or will I mostly be fine with the same hardware for the same amount of traffic (we will try to pack DBs in RAM, of course)?

Visit http://triligon.org

eZ debug

Timing:	Jan 18 2025 15:55:14
Script start
Timing:	Jan 18 2025 15:55:14
Module start 'layout'
Timing:	Jan 18 2025 15:55:14
Module start 'content'
Timing:	Jan 18 2025 15:55:14
Module end 'content'
Timing:	Jan 18 2025 15:55:14
Script end

Main resources:

Total runtime	0.0191 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.0056	587.9141	152.6250
Module start 'layout'	0.0056	0.0030	740.5391	39.4453
Module start 'content'	0.0087	0.0080	779.9844	89.2109
Module end 'content'	0.0167	0.0024	869.1953	34.3047
Script end	0.0190		903.5000

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	14.2138	14	0.0002
Check MTime	0.0012	6.1453	14	0.0001
Mysql Total
Database connection	0.0007	3.7674	1	0.0007
Mysqli_queries	0.0029	15.3634	3	0.0010
Looping result	0.0000	0.0787	1	0.0000
Template Total	0.0019	9.9	1	0.0019
Template load	0.0009	4.8845	1	0.0009
Template processing	0.0010	4.9945	1	0.0010
Override
Cache load	0.0006	3.3963	1	0.0006
General
dbfile	0.0023	12.2757	8	0.0003
String conversion	0.0000	0.0475	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