In 2012 the SAP Benchmark Council Meeting finalized the rules for running SAP Standard Application Benchmarks in Cloud Environments. The rules specify how SAP Standard Application Benchmarks can be performed in Cloud Environments and what customers have to be aware of, when interpreting the benchmark results.
| Date of Certification (mm/dd/yyyy) |
Technology Partner |
Number of records |
Ad-Hoc Navigation Steps/ Hour |
Operating System - Release Database Server |
RDBMS Release |
SAP NetWeaver Release |
Number & Type of Database/Application Servers |
Certification Number |
|---|---|---|---|---|---|---|---|---|
| 01/17/2014 | Amazon Web Services | 500,000,000 | 113,390 | SuSE Linux Enterprise Server 11 | SAP HANA 1.0 | SAP NetWeaver 7.31 | 1 database server: Amazon EC2 cr1.8xlarge, Intel Xeon Processor E5-2670, 2.60 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 20 MB L3 cache per processor, 244 GB main memory; 2 application servers: Amazon EC2 c3.8xlarge, Intel Xeon Processor E5-2680 v2, 2.80 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 25 MB L3 cache per processor, 60 GB main memory | 2014001 |
| 04/10/2014 | Amazon Web Services | 500,000,000 | 137,510 | SuSE Linux Enterprise Server 11 | SAP HANA 1.0 | SAP NetWeaver 7.31 | 1 database server: Amazon EC2 r3.8xlarge, Intel Xeon Processor E5-2670 v2, 2.50 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 25 MB L3 cache per processor, 244 GB main memory; 2 application servers: Amazon EC2 c3.8xlarge, Intel Xeon Processor E5-2680 v2, 2.80 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 25 MB L3 cache per processor, 60 GB main memory | 2014013 |
| Date of Certification (mm/dd/yyyy) |
Technology Partner | Number of records | Ad-Hoc Navigation Steps/ Hour | Operating System - Release Database Server | RDBMS Release | SAP NetWeaver Release |
Number & Type of Database/Application Servers | Certification Number |
|---|---|---|---|---|---|---|---|---|
| 04/11/2014 | Amazon Web Services | 2,000,000,000 | 177,590 | SuSE Linux Enterprise Server 11 | SAP HANA 1.0 | SAP NetWeaver 7.31 | 5 database servers: Amazon EC2 r3.8xlarge, Intel Xeon Processor E5-2670 v2, 2.50 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 25 MB L3 cache per processor, 244 GB main memory ; 3 application servers: Amazon EC2 c3.8xlarge, Intel Xeon Processor E5-2680 v2, 2.80 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 25 MB L3 cache per processor, 60 GB main memory | 2014014 |
| Date of Certification (mm/dd/yyyy) |
Technology Partner | Number of records | Ad-Hoc Navigation Steps/ Hour | Operating System - Release Database Server | RDBMS Release | SAP NetWeaver Release |
Number & Type of Database/Application Servers |
Certification Number |
|---|---|---|---|---|---|---|---|---|
| 05/05/2015 | Amazon Web Services | 5,000,000,000 | 303.270 | SuSE Linux Enterprise Server 11 | SAP HANA 1.0 | SAP NetWeaver 7.40 | 17 database servers: Amazon EC2 r3.8xlarge, Intel Xeon Processor E5-2670 v2, 2.50 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 25 MB L3 cache per processor, 244 GB main memory; 3 application servers: Amazon EC2 c4.8xlarge, Intel Xeon Processor E5-2666 v3, 2.90 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 25 MB L3 cache per processor, 60 GB main memory | 2015019 |
| 05/05/2015 | Amazon Web Services | 5,000,000,000 | 258,020 | SuSE Linux Enterprise Server 11 | SAP HANA 1.0 | SAP NetWeaver 7.40 | 14 database servers: Amazon EC2 r3.8xlarge, Intel Xeon Processor E5-2670 v2, 2.50 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 25 MB L3 cache per processor, 244 GB main memory; 3 application servers: Amazon EC2 c4.8xlarge, Intel Xeon Processor E5-2666 v3, 2.90 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 25 MB L3 cache per processor, 60 GB main memory | 2015017 |
SAP Benchmarks in cloud environments.
Things you should be aware of when interpreting SAP Standard Application Benchmarks in cloud environments results:
Network and Storage are shared resources in typical cloud offerings. There might be a impact from other cloud subscribers on the network and storage performance. Network and Storage SLAs should be defined to minimize the risk of performance impacts.
In a typically Cloud Offering the Customers are connected via a WAN connection (Internet or VPN) to the cloud provider computing center. The performance of the WAN is not part of the cloud provider nor SAP responsibility. Please be aware of this. The Cloud Provider should offer a tool to measure the actual WAN performance from customer location to the Cloud.
Underlying hardware of a cloud container might change over time.
Some SAP applications for example SAP CRM, SAP SRM and SAP EWM benefit from a very good SCU performance in order to ensure fast response times. With changing hardware in a cloud environment there might also be changes in SCU Performance. SLAs should be defined to guarantee a constant Single Computing Unit Performance for constant application performance.
How fast can infrastructure be adapted to customer needs. How big can be the largest container in the Cloud environment, needed for scaling in multitier environments. These are two questions that should be taken into account when you are planning to subscribe to a cloud offering.