Example: Choosing a topology for better performance
WebSphere Application Server provides various Workload Management (WLM) topologies. Two topologies were compared to show how the type of topology you choose can affect performance.
In this comparison, Topology A contains a Web server and a WebSphere Application Server plug-in in front of a cluster of WAS appservers. Each cluster member contains a Web container and an EJB container. Topology B includes a Web server, a plug-in, and a Web container in front of a cluster of EJB containers. In both topologies, Object Request Broker (ORB) pass by reference is selected and the backend database is on a dedicated machine.
Result: Topology A had 10% to 20% higher throughput than Topology B when running the Java 2 Platform, Enterprise Edition Benchmark sample for WebSphere (Trade).
Note: You can download the Benchmark sample for WebSphere (Trade) from the following Web site:
Topology A has an advantage because the Web container and EJB container are running in a single Java virtual machine (JVM). In Topology B, the ORB pass by reference option is ignored between the Web container cluster member and the EJB container member. In Topology A, the EJB container uses the same thread passed from the Web container. The request does not have to be passed from one thread in one JVM to another thread in another JVM.
In this test environment, Topology A had the advantage. However, many factors related to the application and environment can influence your results.
Tuning the application serving environment
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.