I’m curious as to who here has the largest MODx site, in terms of total number of documents being used. Looks can be deceiving as when documents are deleted, their IDs are retired and no longer re-used. You cannot simply look at your most recently created document’s ID and go with that. I’m not sure how to easily go about calculating the number of active documents without digging into the SQL database.
This is by no means the best way to rank size, it was the first thing that came to mind.
On a corporate website that I help operate and maintain daily, the current estimation is at about 800 active documents.
Thomas, I ran the sql report after your post we are at 950 current active documents not 800.
-
☆ A M B ☆
- 2,213 Posts
I know one site with 1588, otherwise most of the sites I deal with are 300 or less. There is also a proof of concept site with 50,000 pages for a new caching system...
-
☆ A M B ☆
- 24,524 Posts
For an enterprise network hardware manufacturer, 11000+ between support intranet and public facing pages.
Evolution or Revolution?
BTW: are there any known limitations in performance issues?
did anyone run a load test or stress test how many simultanously user a MODx (r)evo can stand?
yes I know, there are many many circumstances that may influence the serverload or database activities.
but, let’s say a "normal page", with two wayfinder snippets, some Dittos or Listindexes, two or three jQuery plugins and a couple of images, completed with css and a snippet generated random image transition header to perform on the fly PHP-based file usage.
maybe delivered on a dedicated high end quad core server, with enough RAM and raid-space... or in other words: no worries about the hardware and the internet connectivity ;-)
or, just to face the big ones:
does anyone got an idea for a distributed loadbalanced scenario, with a couple of "MODx slaves"-servers, sharing the same database- and fileserver(s) for a high performance site?
I’m not kidding -- just afraid of Typo3...
cheers,
rolf