Our company is facing some difficulties with our CMS web application. This application was part-built by a contractor and we have been confronting some stability issues (crashing, having to put them in front of load balancers or caching mechanisms) when we think the application should be able to handle it. We put together a minimal standard measurement, but we don’t know if these metrics are realistic.
We were hoping to get in this forum feedback on what is a realistic expectation of a CMS system should handle independent of the technology that was built. So if the same application was to be built in .NET instead of Java (current) you will expect to perform the same.
The metrics that we came up with are:
- Number of concurrent requests/queue length: 100 Maximum
- Time to serve a request: 2 s Minimum
- Number of requests per hour: 150,000
- Minimum number of page views per hour: 5,000
Minimum HD Requirements:
– 2 GB Ram
– 2 Dual-Core 2.0 Ghz
General Functionality:
- Dynamic Cross Referencing (People to
News,Events to People and News,
Technical Cases, Etc) - Advanced Search Features
- Highly Configurable without programming
It’s not reasonable to make concrete performance & scalability expectations without any information about hardware, technology, load, usage, etc. “CMS” is very broad:
Other important questions to answer:
In our farm of several load-balanced 64-bit servers with ~32gb RAM (IIRC) and 4 CPUs each, we average just under 100k requests per hour with a peak load of several hundred requests/sec (uncommon). Total end-user load time (incl images and assets) must be under 5 sec. Our total CMS content database is just under 750,000 pages. We have massive amounts of cross-loaded content, querying, complex editor-configurable widgets, etc.