taiwan apt osm sizing. the sizing estimates contained in this document are based upon the...

Taiwan APT OSM Sizing

THE SIZING ESTIMATES CONTAINED IN THIS DOCUMENT ARE BASED UPON THE ASSUMPTIONS OF PROPER APPLICATION CONFIGURATION AND TUNING, IN A MANNER CONSISTENT WITH BEST PRACTICES OF CGBU CONSULTING AND PERFORMANCE ENGINEERING.THIS DOCUMENT IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY AND IS NOT INTENDED TO BE, NOR SHALL IT BE CONSTRUED AS A COMMITMENT TO DELIVER ORACLE PROGRAMS OR SERVICES. THIS DOCUMENT SHALL NOT FORM THE BASIS FOR ANY TYPE OF BINDING REPRESENTATION BY ORACLE AND SHALL NOT BE CONSTRUED AS CONTAINING EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. YOU UNDERSTAND THAT THE INFORMATION CONTAINED IN THIS DOCUMENT WILL NOT BE A PART OF ANY AGREEMENT FOR ORACLE PROGRAMS OR SERVICES. BUSINESS PARAMETERS AND OPERATING ENVIRONMENTS VARY SUBSTANTIALLY FROM CUSTOMER TO CUSTOMER AND AS SUCH NOT ALL FACTORS WHICH MAY IMPACT SIZING IN YOUR ENVIRONMENT MAY HAVE BEEN ACCOUNTED FOR IN THIS EXERCISE.

Disclaimer

© 2011 Oracle Corporation – Proprietary and Confidential 3

Sizing Parameters

General Information Value Note

Peak orders per hour >10,000 Customer Provided

Concurrent User >30 Customer Provided

Average Tasks per Order 15 Customer Provided

Order lines per Order <50 Customer Provided

Maximum Task per seconds >42 Customer Provided

Peak orders per hour 10,000 Customer Provided

Target CPU Utilization of APP/DB server <70% Customer Provided

Order retention period 12 months Customer Provided

Orders per day 100,000 Assumption

Miscellaneous Assumption Note

Customer already have Load balancer Confirmed with customer, load balancer is recommended for HTTP

Oracle DB failover solution will be used instead of RAC Confirmed with customer


Hardware SolutionCategory Hardware SPEC Solution Remark

Server Server Model SPARC T4-1 In case of T4-1 hit maximum cores limitation, use Sun T4-2 instead for growth

Chip Type SPARC T4 CPU: 8 cores, 64 threads @ 2.85 GHz, Cache:128KB L2, 4MB L3

# of Servers 2 Totally 4 Virtual Machines for 2 APP nodes and 2 database instances

Cores Per Server 2 Totally 4 cores

RAM per server 64GB Totally 128GB RAM, in cause of low price of RAM,

Storage Database Storage (TB) 5TB

APP Server Share Storage

256GB SAN storage for Application Domain / JMS Persistence store, Prefer UFS file system instead of ZFS.

Miscellaneous Load balancer <Using Existing Load balancer>

Network Interface 1Gb Ethernet Across application server, database server, load balancer, SAN. 1Gb Ethernet is sufficient. Link aggregation could be used to create more bandwidth.


Physical Host A: SPARC T4-1

Storage Area Network – RAID10

Zone (3) 1 Core, 8 Gb RAM

Physical Host B: SPARC T4-1

Load balancer

Deployment Diagram

Legend

• Physical Hardware

• Virtual Machine-Zone

• Active Server

• Passive Server

• Logical component

• HTTP(s)Integration

• JMS Integration

• H/A solution

OSM DB Instance 1

Zone (1) 1 Core, 8Gb RAM Zone (2) 1 Core, 12 Gb RAM

OSM Cluster

Managed Server 1

OSM Cluster

Managed Server 2

OSM Cluster – Admin Server


OSM DB Instance 2

Distribute Queue

Hardware Option1 – Using VM

Server Model SPARC T4-1

# of Server 2

Cores per Server Used 2

RAM per Server Used 16 - 20 GB

Fail over

Space for Growth:6 Cores Space for Growth:6 Cores

OSM Cluster


Zone (1) 2 Core, 16Gb RAM

Scalability Options


OSM Cluster

Managed Server 1

OSM Cluster

Managed Server 2

• Extend more cores /RAM

OSM Cluster

Managed Server 4

OSM Cluster

Managed Server 3

OSM Cluster – Admin Server

• Add more servers into cluster

© 2011 Oracle Corporation – Proprietary and Confidential 7© 2009 Oracle Corporation – Proprietary and Confidential

7

Thank You

taiwan apt osm sizing. the sizing estimates contained in this document are based upon the...

Documents