SAP Benchmark

Display Serverdetails

Certified Benchmarks - Help

This site will give you information about all certified SAP Standard Application Benchmarks . Please use the search form to select the bencharks of interest. Rules how benchmark results may be compared are listed in the benchmark publication rules (the rules can be found under Publication Guide -> "SAP Standard Application Benchmark Publication Guide")
The meaning of the keywords in the query-form
Component The benchmark component indicates the SAP component that is mainly tested by the given benchmark.
The componet actually defines the benchmark.
Config There are differnt configurations, depending on the component:
  • 2-tier
    On this configuration, everything runs on one system. This is also called central benchmark, because everything runs on one central server. On this server you will find the database, the dialog, batch and update tasks and the central instance. Only the benchmark driver (the presentation layer) may be on an other server (this makes the second layer from which the name 2-tier comes).
  • 3-tier
    On a three tier configuration, you will normally find the three layers "presentation", "application" and "database" on separate hosts. Because an SAP system can be configured in several ways, there is no rule how the tasks have to be distributed across the servers. A common configuration is, that there is one database server with only the database running on it and one or several application servers. But other configurations have been certified as well.
  • scale-up
    For BWH benchmarks: Every BWH benchmark is a 3-tier benchmark as the applicationserver runs on a different host. But this host is not mentioned in the benchmark certificate as it only plays a minimal role. For BWH benchmarks therefore the distinction in scale-up and scale-out is important.
    In scale-up, the HANA database runs on a single host.
  • scale-out
    In a scale-out configuration, the HANA database runs distributed on several hosts (one master and several slaves).
Release The release indicates the release of the used SAP software. Each benchmark component has it's own releases, e.g. ERP benchmarks have Enhancement package 5 for SAP ERP 6.0, etc., BWH benchmarks have a NetWeaver release etc.
Type On premise or cloud.
"cloud" is considered a different configuration because of some general differences to "on premise" benchmarks. Please find more information about this topic here
Vendor This is the name of the hardware provider.
As a company name is nothing stable, you may find several company names if you choose only one. E.g. if you choose "HPE", you will also find results from HP, Compaq and Digital, or if you choose "Fujitsu", you will also find results from "FSC", "SNI" and "Siemens".
Database This indicates the database software.
Operating System This indicates the operating system of the central server in a two tier configuration. In a three tier configuration, the operatingsystem of the database server is the important thing.
Hypervisor For benchmarks running in a virtualized environment, this will show the used hypervisor.
In cloud environments, typically hypervisors are used but they are not considered like in on premise benchmarks (indicated by "n/a").
Server Type Here you can fill in any string you want. A result is displayed if this string is found somewhere in the server details.
You can therefore search for e.g. CPU-Types (type "8180" to look for all benchmarks running with Intel Xeon Platinum 8180 processor)
Date From and Date To Select the date when the benchmarks have been certified.
BW EML/AML/Edition for SAP HANA: No.of records Some of the benchmarks use a varying amount of initial data. These benchmarks are:
  • BW EML
  • BW AML
  • BW Edition for SAP HANA Version 1, 2 or 3
All of these benchmarks have different rules what number of records are possible (e.g. BW Edition for SAP HANA will have a multiple of 1.3 billion records). Therefore you probably want to select the component first, before selectiong the number of records.
Please note that only those benchmarks can be compared that use the same number of records.
Display Server Details
  • Long: All available data for all servers is displayed
  • Short: Only the type and amount of CPUs is displayed. In a 3-tier configuration, only the number of application servers is shown This will help you to keep a long list readable!
Order by
  • Certification Nr: Ordered like the benchmarks have been certified
  • Result: The number of user or throughput is the sort criteria (depending on the benchmark). This selection will only be visible if the component has been selected (and in case of BWH also the number of records). In benchmarks with multiple KPIs it is not alway possible to have a clear order: If one KPI is better, but the other one worse, this actually can not be sorted. On this page, one of the KPIs is picked as for sorting - but as mentioned - this might not be correct.
The meaning of the keywords in the result list
Nr This is the unique certification number.
Date The date, the benchmark was certified.
Vendor The hardware provider.
Component The benchmark component (like SD, ATO, etc.).
Throughput The throughput is the result of the benchmark. The unit is depending on the component. E.g. SD benchmark generates a throughput value of "SAPS", the ATO benchmark generates "orders/h". There are benchmarks that will have more than one value displayed. These benchmarks have more than one KPI as a result and each of the KPIs is displayed with its unit of measure.
User For dialog benchmarks, users are the main result. The users are simulated benchmark users with a thinktime of 10 seconds. By doing their work, they will create the shown throughput.
Rsp The dialog response time for dialog benchmarks. This is the response time in seconds, the users sees when he sends a screen to the SAP system.
Config Configuration 2-tier or 3-tier or in case of BWH scale-up or scale-out. If nothing else is show, this is an "on premise" benchmark. In case of a cloud environment, the word "cloud" is added.
Release Release of the used SAP software.
DBMS Database server type and version.
OS Operating system release. In a 2-tier configuration this is the OS version of the central server, in a homogenous 3-tier configuration (all servers use the same OS) this is this one used OS, in a 3-tier heterogenous configuration, the different OS versions are shown.
In virtualized benchmarks, the virtualisation software is displayed in this column.
System A detailed description of the used servers:
  • CENT The central server in a 2-tier configuration
  • DB The Database server
  • DB-Master The Master node in a HANA scale-out.
  • DB-Slave The Slave nodes in a HANA scale-out
  • Dia Dialog servers
  • Upd Update server
  • Msg The message server
  • Enq The enqueue server
  • ITS Internet Transaction Server
If there are several tasks on one server this is indicated by task1+task2+....