Hi,
how many pages can modx revolution handle before it will slow down? 100? 1000? 10,000?
regards
cronix
-
☆ A M B ☆
- 2,475 Posts
This is an interesting topic -- that other thread is good reading too.
What I’d love to see is some case studies... I looked at a Revo site last night that had about 150k pages, and the performance was not very good (sorry, no exact numbers here), but it’s too simplistic to point the finger at MODx. The server had some CPU throttling going on, and it only had 1GB of RAM, and PHP was configured to use ALL of it. The pages utilized perhaps 10 template variables, and WayFinder calls listed contents of a a particular folder. The error logs showed PHP requesting about 10 times the amount of memory available. Granted, putting the custom content into an optimized database table with proper indexes etc. would have made the queries MUCH more efficient, and I think this would have percolated down to xPDO requiring far less memory -- the JOIN statements required to assemble values of 10 template variables does spike the MySQL resources required.
It’d be a worthwhile endeavor to benchmark MODx with certain server limitations. E.g. hold TVs and server RAM constant, and then track PHP memory use while increasing the number of pages. Or hold the # of pages constant and then track PHP memory use and MySQL query time as you add more and more TVs to a series of pages. Or simply do a side-by-side comparison of having pages with TVs compared to having a custom database table.
Anyone else got ideas for benchmarks? Anyone got an unused dedicated server they’d like to volunteer for this type of thing?
