Identify three reasons that explain why assigning more than one managed serve achieve better
performance than running one managed server with more resources?
A.
Thread management inside the JVM process might be less effective than context switching
between processes on the OS level. It is better to combine both these technologies to achieve full
saturation of resources.
B.
Current CPUs are multicore units. So starting managed servers in the amount of physical cores
and pinning them 1:1 to cores will always get the best performance.
C.
By a combination of prioritization of processes on the OS level and Work Manager in WLS, one
could tune the whole environment more precisely.
D.
Assigning more than one managed server to hardware will never bring better performance.
E.
More instances means more connections to databases, so one could serve more concurrent
calls on the database level. This is primarily why this approach will give better performance
numbers.
F.
Depending on the profile of the application, having more JVMs with smaller heaps will lead to
more predictable response times than fewer JVMs with a large heap.
Explanation:
Note:
* Two or more Managed Servers can be configured as a WebLogic Server cluster to increase
application scalability and availability. In a WebLogic Server cluster, most resources and services
are deployed identically to each Managed Server (as opposed to a single Managed Server),
enabling failover and load balancing. A single domain can contain multiple WebLogic Server
clusters, as well as multiple Managed Servers that are not configured as clusters. The keydifference between clustered and non-clustered Managed Servers is support for failover and load
balancing. These features are available only in a cluster of Managed Servers.
* A WebLogic Server cluster provides these benefits:
Scalability
The capacity of an application deployed on a WebLogic Server cluster can be increased
dynamically to meet demand. You can add server instances to a cluster without interruption of
service—the application continues to run without impact to clients and end users.
High-Availability
In a WebLogic Server cluster, application processing can continue when a server instance fails.
You “cluster” application components by deploying them on multiple server instances in the
cluster—so, if a server instance on which a component is running fails, another server instance on
which that component is deployed can continue application processing.