Note that there are some explanatory texts on larger screens.

plurals
  1. POMaximum concurrent users for JSF2?
    primarykey
    data
    text
    <p>I am working on a Java Web Application, using the following frameworks : Spring 3.1, JSF 2.1.26 and RichFaces 4.3.3. The whole app is running in the Amazon Cloud under medium.m1 instances (2 - 2.4 Ghz single core), with a Tomcat 7.</p> <p>My customer asked questions about the performances of the web application, and about the number of concurrent users that can be handled on the same server. He gave me a report showing that a servlet with about the same hardware than the Amazon medium one is able to serve about 1000 requests per seconds (40KB page) : <a href="https://www.webperformance.com/library/reports/windows_vs_linux_part1/" rel="nofollow">https://www.webperformance.com/library/reports/windows_vs_linux_part1/</a></p> <p>I took a classic page with header/footer, data table, sort/search/filters/data scroller... (80KB). I removed the database, the filters (security, etc., except JSF one) and kept 20 visible rows. Without any load, that page takes about 300 ms to be loaded.</p> <p>When I executed the load test for my application, I realize that it can only serve 20 requests per second before the request/response time exceeds the 1000 ms. Can you tell me if this is a normal behavior? I can understand a JSF page is longer to build than a simple servlet one, but not being able to serve more than 20 requests, while the servlet can serve 1 000 is puzzling.</p> <p>Is there any standard benchmark for a typical JSF application? If you think I have optimization problem, can you tell me where I can search?</p> <p>Thanks in advance for your answer!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload