java - What is a realistic measurement to load test a CMS web application? -


Our company is facing some difficulties with our CMS web application. This application was made by a contractor and we are facing some stability issues (placing them in front of the load balancer or caching system) when we feel that this application should be able to handle it. We have kept a minimum standard measure, but we do not know whether these metrics are realistic.

We were hoping to give feedback on this platform about the realistic expectations of the CMS system, which was created Must be different from technology. So if the same application was created in NAT instead of Java (current), then you would also expect to do the same.

The metrics we have come up with are:

  • Concurrent request / number of queue: 100 max
  • Time to request: 2 S minimum
  • Number of requests per hour: 150,000
  • Minimum number of pageviews per hour: 5,000

Minimum HD requirements: - 2 GB Rama - 2 Dual-Core 2.0 Giz

General functionality:

  • Highly configurable without programming
  • < Li> ul>

It is not appropriate to perform solidly & amp; Scalability requirements "CMS" is very detailed without any information about hardware, technology, load, usage etc.:

  • How does your server look like?
  • What is the terms of your SLA?
  • What does your typical user look like? Like many concise users or users with fewer users or fewer requests and many more requests?

Other important questions to answer:

  • Are you "first byte
  • how many editors are working against the system ?
  • Do your editors work against the support of the same data, or do they prepare content in a separate environment and suppress the batches of content updates?
  • You What kind of caching system can support? Can the content be for the minutes / hours old?

~ In our field of many load-balanced 64-bit servers with 32 GB RAM (IIRC) and 4 CPUs, we can provide a peak load of just several hundred requests / seconds (unusual) below 100 Requests per hour with total end-user load time (including images and assets) should be less than 5 seconds Our total CMS content database is just under 750,000 pages. We have large-scale cross-loaded content, queries C, complex editor-configurable widget, etc.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -