Capacity of MODx

Hi,

Don’t know if it’s been tested, but does anyone have any evidence as to how MODx would handle an extremely large website? For instance, maybe 2000+ pages (most unpublished), plus an image gallery (using Easy2Gallery extra) of upto 1mil images. These are obviously extreme figures, but knowledge of this would be most helpful.

Thanks.

Depends. 1.0.x Evolution by default starts to slow down at ~ 5,000 documents, but somebody has a different caching scheme that overcomes this. 2.0 Revolution doesn’t have the limitation at all. I would think that if your images were organized in some manner they wouldn’t be a problem, but I also think that anything is going to have a problem if all 1mil images are dumped in one directory.

Quote from: moniarde at Apr 20, 2010, 03:01 AM

Hi,

Don’t know if it’s been tested, but does anyone have any evidence as to how MODx would handle an extremely large website? For instance, maybe 2000+ pages (most unpublished), plus an image gallery (using Easy2Gallery extra) of upto 1mil images. These are obviously extreme figures, but knowledge of this would be most helpful.

Thanks.

just out of curiosity... 1mil is 1 million images?

That would be more dependent on your database configuration, how you choose to serve the images and your server configuration. There’s no inherit limitation in MODx that would make that fail. For that number of images and assuming a large amount of traffic, I’d personally offload images to a mirror-bucket-type CDN and create a custom gallery script that works with caching.