What is the limit of documents modx 1.0.4 can hendle?

Hello,
My clint would like to have an online catalogue with about 30 000 products. I’d like to have each document representing a product. But I don’t know if modx evo 1.0.4 can hendle this amout o pages?
Please advice me ...
regards,
luke

Hi Luke,

MODx Revolution should be capable of managing that, as its caching is done in such a way there’s not one big cache file it needs to load every request.

I’m not sure if 1.0.4 has improved caching also, but the older versions (before 1.0.0 for sure) have a limit of aprox 5000 docs.


If you’re going to have such a big catalog, isn’t it better to use a custom table for that information, rather then putting everything in a document/resource? You could easily make a snippet to display the requested information. If needed you could make a module to maintain the items.

This makes me think if you really need that much items though, I bet there’s different varieties of the same item you could combine?


As a side note, I don’t think there’s any CMS you would want to use if you are maintaining 30K resources.

Quote from: Mark at Jul 08, 2010, 05:08 AM

MODx Revolution should be capable of managing that, as its caching is done in such a way there’s not one big cache file it needs to load every request.

This is a common misconception. It still has a cache file of all the Resources in each Context, so unless you are putting 1000 into each Context, you would have to completely disable Context caching to work with 30000 Resources in a single Context. This is not the proper way to use MODx.

Quote from: Mark at Jul 08, 2010, 05:08 AM

I’m not sure if 1.0.4 has improved caching also, but the older versions (before 1.0.0 for sure) have a limit of aprox 5000 docs.

FWIW, this is not a limit, but a guideline, based where performance begins to degrade on a typical hosting environment.

Quote from: Mark at Jul 08, 2010, 05:08 AM

If you’re going to have such a big catalog, isn’t it better to use a custom table for that information, rather then putting everything in a document/resource? You could easily make a snippet to display the requested information. If needed you could make a module to maintain the items.

As a side note, I don’t think there’s any CMS you would want to use if you are maintaining 30K resources.

A CMS is for managing content, not data. By using a CMS, you should expect it to help you present and manage our content, but not necessarily manage your catalog inventory. For this, you create custom storage (or use a web service or whatever). But making each item a Resource is not the proper way to use a CMS.

What you could do in either Revo or Evo is build pages or views from which your client could administer external table data. In Revo you could leverage the EXT grids to display the table data and create bulk actions and add a custom item editors directly in the manager as part of the 3rd party component but, as was mentioned, you shouldn’t use a CMS to operate as a mid size e-commerce platform and expect it to perform well.