WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

Intelligent runtime provisioning
The new intelligent runtime provisioning function is disabled by default. You might
want to enable it in the Integrated Solutions Console to reduce the startup time
and resource consumption. Improvements in the startup time of up to 10-15%
can be seen. For more information about intelligent runtime provisioning see
3.1.14, “Intelligent runtime provisioning” on page 72.
Workload profile setting
WebSphere Application Server for z/OS V7.0 introduces a new value for the
workload profile setting in the Object Request Broker (ORB) services advanced
settings.
It is now possible to make a user defined selection for the number of threads,
using the CUSTOM setting.
To change the value through the Integrated Solutions Console, click Servers →
Server Types → WebSphere application servers → your_server →
Container services → ORB service → z/OS additional settings.
Table 14-6 lists all possible values.
Table 14-6 Workload Profile settings for z/OS ORB service
Value # Threads Description
ISOLATE 1 Specifies that the servants are restricted to a single
application thread. Use ISOLATE to ensure that concurrently
dispatched applications do not run in the same servant. Two
requests processed in the same servant could cause one
request to corrupt another.
IOBOUND MIN(30,
MAX(5,(Number of
CPUs*3)))
CPUBOUND MAX((Number of
CPUs-1),3)
Specifies more threads in applications that perform
I/O-intensive processing on the z/OS operating system. The
calculation of the thread number is based on the number of
CPUs. IOBOUND is used by most applications that have a
balance of CPU intensive and remote operation calls. A
gateway or protocol converter are two examples of
applications that use the IOBOUND profile.
Specifies that the application performs processor-intensive
operations on the z/OS operating system, and therefore would
not benefit from more threads than the number of CPUs. The
calculation of the thread number is based on the number of
CPUs. Use the CPUBOUND profile setting in CPU intensive
applications, like XML parsing and XML document
construction, where the vast majority of the application
response time is spent using the CPU.
468 WebSphere Application Server V7.0: Concepts, Planning, and Design