Performance Tuning Goals for WebLogic Server

In general, performance tuning involves inspecting a fully functional and operational technical domain for potential inefficiencies (bottlenecks) and resolving (tuning) any identified inefficiencies so that an improved level of behavior can be achieved from that target technical domain. In the context of WebLogic Server, performance is measured through three interdependent behaviors:

• Response Time ” The duration of time the WebLogic Server takes to provide a response to an incoming request

• Throughput ” The number of clients WebLogic Server can service at any given point in time

• Latency ” The roundtrip time it takes a client to make a request to WebLogic Server and for WebLogic Server to fulfill that request and provide a response back to the calling client

If you want to achieve the optimum performance from your WebLogic Server, increasing the server's response time and throughput and decreasing any latency should be your goals. The scalability of WebLogic Server is also affected by its performance because business requirements to introduce additional concurrent users or resources, such as applications, should be facilitated without any degradation to WebLogic Server's performance.