234 IBM Enterprise Workload Manager
? Total java heap usage This is simply adding the domain manager java heap size to the
Control Center java heap size.
? EWLM DB size: The domain manager and WebSphere Application Server processes
both have embedded internal database instances to house persistent data such as
policies, server information, one minute reporting data, and so forth. This field represents
the combined disk requirements witnessed for these databases. In our tests, the largest
disk consumer was domain manager's EWLM Data Reporting database (houses 1 minute
reporting data utilized for CC interval reports). This database was responsible for more
than 95% of the total database disk requirements.
? Elapsed Time: 60min Interval Report represents the Elapsed Time of requesting a 60
minute Monitor-Transaction Classes report from the EWLM Control Center. We think this
command is the most data-intensive report request from the Control Center because it
requires reading data for all transaction classes, so we utilized this metric as a measuring
stick of Control Center responsiveness.
9.2.10 General sizing recommendations on i5/OS
Based on our internal testing, we offer the following general sizing guidance.
Minimum system requirements
A 700 CPW iSeries with 1.5GB memory is the minimum system recommended for a domain
manager that is handling 63 or fewer managed servers and a policy of 40 transaction/process
classes and 10 service classes.
General system requirements guidance
? 100 to 300 managed servers with a policy up to 80 transaction/process classes and 20
service classes should safely fit on a 1100 CPW iSeries with 2GB RAM.
? 300 to 500 managed servers with a Policy up to 80 transaction/process classes and 20
service classes should safely fit on a 2200 CPW iSeries with 2.5GB RAM.
? Domain manager initial heap settings need to be adjusted to fit the particular combination
of available CPU and memory. Higher CPW configurations can use less memory by
increasing the initial heap size. Configurations with more memory can use less CPU by
decreasing the initial heap size. To reduce both memory and CPW requirements, first
reduce the policy complexity, then reduce the number of managed servers.
? We suggest monitoring memory and processor resource usage as the configuration grows
to more than 100 servers to more accurately project your requirements for these larger
configurations.
? Beyond product install disk requirements, an additional 1GB of disk space should be
sufficient for EWLM's database requirements.
Memory guidance
Ensure sufficient physical memory to back the domain manager and WebSphere Application
Server processes. We recommended that you monitor the memory and the processor
consumption of these processes upon any substantial changes to size or policy complexity of
the management domain, for example, going from 10s to 100s of managed servers or 10 to
50 transaction classes.
Recall that the memory footprint of the domain manager can be quickly reduced by using a
less complex policy. Increased CPU utilization can be exchanged for a reduction in the
memory footprint of the domain manager by reducing the initial heap size. If paging is
observed and there is surplus CPW, consider adjusting the heap size first. If paging is
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.