Scalability issues - Websphere

This is a discussion on Scalability issues - Websphere ; Hi, We have a web application on WebSphere Application Server(WAS) which doesn't have any core application logic but is just used to communicate to an application on another machine using RMI. We have performed load testing (75 concurrent users) of ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Scalability issues

  1. Scalability issues

    Hi,

    We have a web application on WebSphere Application Server(WAS) which doesn't have any core application logic but is just used to communicate to an application on another machine using RMI. We have performed load testing (75 concurrent users) of the application and found that the TPS is 160 and it saturates at 37 users. To confirm whether the web application is a bottleneck, we have performed a test with two WAS instances. The 75 user test has now given an increased throughput of 230, a significant increase over the previous throughput of 160. This test confirmed that there is a bottleneck in the web application. Then, we profiled the application and found that there are no bottlenecks in the code. Does it conclude that the problem is in configuring WAS? We have increased the threadPool size of WebContainer to 100 and found that the TPS now saturates at 67 users, but the TPS has gone down to 130.

    What does the threadPool of web container signify? Does it really improve scalability?

    Are there any other ways of improving scalability of WAS? What is the ideal configuration, because once we have increased the threadPool size of WebContainer to 100, though the TPS saturated at 67 users, it has gone down drastically.

    The problem is not there in the RMI application, as it is able to scale up in case of 2 WAS instances.

    Any help is highly appreciated.

    Thanks,
    Ujval

  2. Re: Scalability issues

    What about DB connection pool settings? Are you monitoring DB ? Hows performance of DB?
    Another check, max and memory? Enable verbose gc and try to monitor hows GC performing?
    One more thaing, Session, what is the size of session? How you are persisting?

  3. Re: Scalability issues

    ujval_mysore@infosys.com wrote:
    > Hi,
    >
    > We have a web application on WebSphere Application Server(WAS) which doesn't have any core application logic but is just used to communicate to an application on another machine using RMI. We have performed load testing (75 concurrent users) of the application and found that the TPS is 160and it saturates at 37 users. To confirm whether the web application is a bottleneck, we have performed a test with two WAS instances. The 75 user test has now given an increased throughput of 230, a significant increase over the previous throughput of 160. This test confirmed that there isa bottleneck in the web application. Then, we profiled the application and found that there are no bottlenecks in the code. Does it conclude thatthe problem is in configuring WAS? We have increased the threadPool sizeof WebContainer to 100 and found that the TPS now saturates at 67 users,but the TPS has gone down to 130.
    >
    > What does the threadPool of web container signify? Does it really improve scalability?
    >
    > Are there any other ways of improving scalability of WAS? What is the ideal configuration, because once we have increased the threadPool size ofWebContainer to 100, though the TPS saturated at 67 users, it has gone down drastically.
    >
    > The problem is not there in the RMI application, as it is able to scaleup in case of 2 WAS instances.
    >
    > Any help is highly appreciated.
    >
    > Thanks,
    > Ujval
    >

    Tuning a multi-tier JEE application is fairly complex. You may have
    profiled your application, but the same tool should be able to do the
    same for the application server. In addition, there's the Tivoli
    Performance Viewer in WAS that can help pinpoint bottlenecks. It even
    comes with some kind of advisor.

    'Performance Analysis for Java Web Sites' is a pretty
    good book for doing this kind of work, if I do say so myself


    Ken

+ Reply to Thread