JSF Performance Limit

I have a kind of unusual question, and I know this is very controversial, but here it comes.

In the past, I have developed several JSF applications, but all this limits the number of users that can be transferred around 5-6. This was partly due to license-based policies. I ran several tests with over 20 users and Selenium, and the applications went very slowly. The problem is probably related to server performance, but I cannot help asking the following question:

Can a JSF application support a large number of users? My bet will be that the framework should allow this, however I cannot think of any commercial website that uses JSF and can support thousands of users at a time. (If you could show me that would be great!)

I ask about it because I was asked to develop a larger system, and I would like to use JSF because I really like it, but recent performance tests have given me doubts. The lead programmer said that this is a problem only for the server machine, but in which case, which machine can support thousands of users registered at the same time? The lead programmer is not the best of them kind, so I want to hear a second opinion from SOF, if you don't mind.

If any structure is more suitable for extreme use, please tell me what it is, the only real limitation I have is that it must be Java on the server side.

Again my apologies for the unconstructive question.

+8
java performance jsf jsf-2
source share
2 answers

all this limits the number of users that can be transferred around 5-6

Not sure what the app download or design is, but it sounds incredibly low. JSF should be able to handle many 100 users if they are created correctly or even 1000 with the right infrastructure. JSF code works with servlets and facelets - the framework is the standard code on top of them that has been optimized over time and optimized by JIT at runtime.

eg. With IBM Websphere Portal Server and Oracle Portal, JSF is the standard way to create client portals and applications. And they are used in massive installations.

It looks like your past application (s) was having problems. I do not think you can blame this performance with JSF.

+5
source share

If you want the extreme number of connections to be Java, you can consider http://netty.io/ It is designed to be supported and has been tested on 100,000+ connections.

I suspect that the bottleneck is not the number of connections you have, but how efficiently you serve pages, i.e. you jsf are especially slow. If you optimize what I suspect, you can handle more connections.

+1
source share

All Articles