Forums / General / Scalability with a LOT of content
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.
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)?
Script start
Module start 'content'
Module end 'content'
Script end
Time used to render debug report: 0.0001 secs