November 16, 2010

Oracle PeopleSoft Sizing Estimate for The

Methodist Hospital System
System x Hardware

© 2010 IBM Corporation

Introduction
1. IBM is pleased to provide a sizing estimate for IBM hardware running Oracle software. This sizing
estimate describes the IBM hardware resources required to support the proposed The Methodist
Hospital System installation as described in the input documents and as described in the following
sizing assumptions.

2. This sizing estimation includes a workload from a provider other than IBM. IBM is not responsible
for the accuracy of the data contained in such a workload. Any reliance by you on the third party
workload is at your sole risk and will not create any liability or obligation for IBM. If you have any
questions or are unsatisfied with the third party workload information, you should contact the third
party provider.

3. The system resources quoted to you in any sizing related communications are sufficient only for the
workload(s) estimated. Other factors may require additional resources (e.g. additional non-
estimated workloads, minimum configurations for RAID, allowance for growth, workspace, etc).

4. The information provided to you in any sizing related communications are provided by International
Business Machines Corporation (IBM) as a service to you and may be used for informational
purposes only. Use of any sizing related communications is restricted to the purpose of helping you
predict a possible IBM System Server model processor, memory and disk resources for a given
workload. All representations of processor utilization, throughput, response time, memory, disk,
and other performance data in the sizing communications are estimates and averages based on
certain assumptions and conditions. No representation is made that these throughputs and their
corresponding response times or other performance data will be accurate or achieved in any given
IBM System Server installation environment. They are based on specific configurations and run time
environments. Customer results will vary. Any configuration recommended by the sizing information
communicated should be tested and verified. By accepting this information or using the sizing
details you agree to the terms and conditions contained herein. If you do not agree with such terms
and conditions, please do not review or use the provided materials and return the materials to IBM.

© 2010 IBM Corporation

2
Sizing Methodology & Assumptions
ƒ We used an application predictive sizing based on IBM’s Oracle PeopleSoft sizing methodology and sizing tool developed by
the IBM International Oracle Competency Center.
ƒ This sizing reflects the resources consumption for the workload described in the original sizing questionnaire named
“TMHS_RESPONSE_20100405.doc “ and recommendations described in the sizing deliverable named “The Methodist
Hospital System - IBM PeopleSoft Enterprise Deliverable 24May2010.pdf “. There has been no changes to the workload as
previously defined in these documents.
ƒ Oracle Enterprise Linux is not a server proven System x Operating System. It is assumed that its performance
characteristics are similar to a distribution of Red Hat Enterpise Linux running on System x.
ƒ For MicroSoft SQLServer we assumed MSSQL Server 2008 and Windows 2008 servers.
ƒ Oracle’s formal statement regarding VMWare supporting is documented in their support web site per note #249212.1
"Support Position for Oracle Products Running on VMWare Virtualized Environments“.
ƒ We assumed no level of virtualization in the database servers.
ƒ We assumed a target CPU utilization of 65% or less. Memory recommendation is calibrated to match best practices,
example, 8GB per core for PeopleSoft workloads.
ƒ The Hyperion sizing was provided by Oracle. Hyperion assumes 2 Planning Applications, 150 active users planning and
workforce.
ƒ OBIEE sized for 300 total users with a 10% concurrency rate.
ƒ For scale out option we assumed Oracle 11gR2 with RAC running on RHEL 64-bit. The sizing was done so that if a node
fails the remaining nodes will be able to sustain the workload.

© 2010 IBM Corporation

3
Sizing Recommendation for Option 1 - RAC

© 2010 IBM Corporation

4
Sizing Recommendation for Option 2 – Cold failover

© 2010 IBM Corporation

5
Sizing Recommendation Hardware List
OPTION 1 – RAC

Middle-Tier – Qty 3
IBM System x3850 X5
2 x Xeon X7560 2.26GHz/8C
128GB memory
4 x Dual-Port NICs

Database – Qty 5
IBM System x3690 X5
2 x Xeon X7560 2.26GHz/6C
96GB memory
2 x Dual-Port NICs for RAC Public
2 x Dual-Port NICs for RAC Interconnect
2 x Dual-Port HBAs

OPTION 2 & 3 – Cold Failover using Linux Cluster,

Oracle RAC One, or MSSQL Server using MSCS

Middle-Tier – Qty 3
IBM System x3850 X5
2 x Xeon X7560 2.26GHz/8C
128GB memory
4 x Dual-Port NICs

Database – Qty 3
IBM System x3890 X5
4 x Xeon X7560 2.26GHz/8C
192GB memory
2 x Dual-Port NICs for Public network
2 x Dual-Port NICs for Private network (cluster)
2 x Dual-Port HBAs

© 2010 IBM Corporation

6
Discussion points
Growth projections. Did the input to sizing included business growth projections. Each hardware was sized at less than 65%
utilization but Option 2 & 3 lock you in a scale up scenario.

Oracle has a firm policy on using 3rd party virtualization products. Will TMHS need to carry an environment that is not
virtualized to comply with Oracle’s policy ?

Oracle database cold failover using Linux Clustering is not commonly seen. Oracle RAC One or a manual cold failover
strategy could be deployed.

For X5 servers, System x3690 is a 2-socket server and System x3850 is a 4-socket server. For optimal performance is
recommended that all sockets be populated in these servers.

Will the existing SAN support the required new workload ? capacity and performance wise ?

© 2010 IBM Corporation

7