Skip to Content
Contact Us

SAP Concurrent Benchmark

The newest member in the family of SAP Standard Application Benchmarks is called Concurrent Benchmark. To demonstrate the power of today´s hard- and software it is now possible to run several benchmarks – be it of the same type or different types – on the same infrastructure. Key to the concurrently running benchmark is that they share a common resource. The so called shared resource could be for example the server, the storage or the network.

Benchmark Definition and Methodology

1. Definition of a "single benchmark" and "concurrent benchmark".

A "single benchmark" is defined as a benchmark against one database with one SAP SID. A "concurrent benchmark" is defined as the parallel execution of several (two or more) single benchmarks at the same time. "One" concurrent benchmark therefore consists of several single benchmarks.

Each single benchmark out of a concurrent benchmark has to be a valid benchmark that fully complies to all rules.

All single benchmarks out of a concurrent benchmark have to have a common highload interval. This interval is defined as follows:

If only dialog benchmarks are involved, the common highload interval for all benchmarks is defined as the overlap of all single benchmarks. This interval has to be at least 15 minutes. A highload interval for batch benchmarks is currently not defined.

There have to be shared resources, which have to be listed in the certificate. For example:

  • OS
  • System (as defined in the "two-tier definition")
  • Storage system
  • Database
  • Network
 

2. Certification of concurrent benchmarks

The certification has two parts:

  • Part 1 shows the summary of the results and the concurrent setup
  • Part 2 lists all involved single benchmarks
 

2.1 The summary will include the following data:

  • Number of single benchmarks
  • Description of the configuration
  • Shared resources
  • One certification number
 

2.2 The list of all involved single benchmarks will contain all the data that is required as the "minimum data" defined in the publication rules.

 

3. Publication rules

The general publication rules as defined in the publication guide (e.g. minimum data, etc.), also apply to concurrent benchmarks. In addition the following requirements must be fulfilled:

3.1 It is not allowed to sum up users or throughput. E.g. it would be allowed to say "we achieved 10 times 100 users", but it is not allowed to sum this up to "we achieved 1000 users".

3.2 Condensed information is allowed if equal systems or releases are used. E.g. - "SAP enhancement package 5 for SAP ERP 6.0 for all systems"

  • "10 times productname each having 4 CPUs,
  • 2 GHz, ..."

3.3 The "shared resources" are part of the minimum required data for concurrent benchmarks.


For further details regarding Publication rules please see the SAP Benchmark Publication Guide.

SAP Concurrent Benchmark

Date of Certification (mm/dd/yyyy)   Technology Partner   Number of Concurrent Benchmarks   Shared Resource(s)   Benchmark Results   Certification Number
12/19/2016   HPE   2   Server   2016066_1:
Benchmark Type: SD
SD Benchmark Users: 74,134
SAPS: 404,750
2016066_2:
Benchmark Type: SD
SD Benchmark Users: 74,134
SAPS: 404,670
  2016066
11/28/2016   HPE   2   Server   2016058_1:
Benchmark Type: SD
SD Benchmark Users: 74,014
SAPS: 405,480
2016058_2:
Benchmark Type: SD
SD Benchmark Users: 74,014
SAPS: 404,320
  2016058
11/07/2016   HPE   2   Server   2016053_1:
Benchmark Type: SD
SD Benchmark Users: 71,030
SAPS: 392,600
2016053_2:
Benchmark Type: SD
SD Benchmark Users: 71,030
SAPS: 397,450
  2016053
01/30/2015   Cisco   2   Server   2015002_1:
Benchmark Type: SD
SD Benchmark Users: 7,584
SAPS: 41,470
2015002_2:
Benchmark Type: SD
SD Benchmark Users: 7,391
SAPS: 40,370
  2015002
Back to top