With the maturity and breadth of cloud solutions, more enterprises are moving mission-critical workloads to the cloud. American Commercial Lines (ACL) recently migrated their Oracle ERP to AWS. ERP solutions such as Oracle E-Business Suite require specific knowledge in mapping AWS infrastructure to the specific configurations and needs of running these workloads. In this session, Apps Associates and ACL walk through the considerations for running Oracle E-Business Suite on AWS, including deployment architectures, concurrent processing, load balanced forms and web services, varying database transactional workloads, and performance requirements, as well as security and monitoring aspects. ACL shares their experiences and business drivers in making this transition to AWS.
13. Enterprise storage requirements
•Requires consistent performance, each application has unique requirements
NAS etc..
Performance
•Addressed by using RAID, Disk Backups, Tape Backups
Durability and availability
•Requires high CAPEX
Cost
•Often addressed by over provisioning
Elasticity and scalability
performance; •Addressed by storage layers like SSD, SAN, NAS, etc..
disk backups, tape backups
over-
14. Enterprise storage on AWS
•Requires consistent performance, each application has unique requirements
•Addressed by storage layers like SSD, SAN, NAS etc..
Performance
•Addressed by using RAID, Disk Backups, Tape Backups
Durability and availability
•Requires high CAPEX
Cost
•Often addressed by over provisioning
Elasticity and scalability
•Provisioned IOPS, SSD, Amazon Elastic Block Store (Amazon EBS) Optimized Instances
•Built in replication across AZ; snapshots can be replicated across regions
Pay for what you use, buy vs. build
Use as little or as much as you want or need
15. Storage option
General
Database
Applications
Speed
Durability
Instance store
Swap
Temporary files
Reports cache, web server cache
Very low latency
Very low; volatile
EBS—PIOPS
Data files, redo logs
Low latency
Moderate; needs to be backed up regularly
EBS
Boot volume
Binaries, archive logs
Binaries
Moderate latency
Moderate; needs to be backed up regularly
Amazon S3
Backups
Backups
Backups
Longer latency
Very high durability
Amazon Glacier
Long-term backups
Long-term backups
Long-term backups
Restore times of 3–5 hours
Very high durability
16.
17. SGA
Buffer Cache
100% cache hit ratio is ideal for OLTP workloads
18. Cache miss
Cache Hit
SelectUpdateSelectUpdateDisk I/O TimeCPU Time
19. 2. User volume is increasing...
1. Data size is increasing...
SGA
1. Huge amounts of data
2. Not possible to cache all data
3.Many I/O operations
Buffer cache
Source: Oracle Corporation
20. Impact of I/O on CPU response times
0.00
2.00
4.00
6.00
8.00
10.00
12.00
14.00
16.00
0
100
200
300
400
500
600
700
800
100
200
300
400
500
600
700
800
Response Time(Normal- 100Thread=>1.00)
TPS(Normal-100Thread=>100)
Thread
TPS
RES
I/O bottleneckLow throughput and slow response
Low CPU usage
Source: Oracle Corporation
21.
22. Storagetype
Comments
Binaries
EBS volume
Standard volume;
EBS snapshots enabled
Data files
PIOPS—EBS volumes
Stripedacross multiple volumes using ASM or any other technology
PIOPS of 1000 or above
Redo log files
PIOPS—EBS volumes
Use separate EBS volumes for each group
Preferable to use ASM disk groups
Archive log files
EBS volumes
Standard volumes fornormal database workloads
PIOPS for highly transactional environments
Backup files
EBS volumes / Amazon S3
Standard EBS volumes for local backups
Use OSB / other technology to push to Amazon S3
23. Amazon S3 Bucket
Amazon Glacier
Life
Cycle
Policies
+DEV_DATA
4 EBS
Volumes
500 PIOPS
DEV TEST
Striping
+PROD_DATA
4 EBS
Volumes
4000 PIOPS
+PROD_FRA
4 EBS
Volumes
1000 PIOPS
PROD
Striping Striping
ASM instance with 16,000+ IOPS