Skip to Content
Contact Us

ERP

ERP

Assemble to Order

The Assemble-to-Order (ATO) Benchmark integrates process chains across SAP Business Suite components. The ATO scenario is characterized by high volume sales, short production times (from hours to one day), and individual assembly for such products as PCs, pumps, and cars. In general, each benchmark user has its own master data, such as material, vendor, or customer master data to avoid data locking situations. However, the ATO Benchmark has been designed to handle and overcome data locking situations – the ATO benchmark users access common master data, such as material, vendor, or customer master data.

 

Benchmark Results

 
Technical Components

Financials CO-OM, CO-PC, FI-GL
Logistics MM-IM, LE-WM, LO-VC, CS, SD-BIL, SD-SHP, SD-SLS, PP-BD, PP-ATO
Basis BC-BMT, BC-SRV
Human resources PD-OM
Cross application CA-CL

Published results of the ATO Benchmark contain throughput numbers; for example 2,500 assembly orders per hour. An assembly order is a request to assemble pre-manufactured parts and assemblies to finished products based to an existing sales order.

Collapse
Dialog Steps
  • 0. Logon
  • 1. Main screen
  • 2. Call /nVA01 (create customer order)
  • 3. Enter order and organizational data
  • 4. Enter customer and material
  • 5. First level characteristic value assignment
  • 6. Second level characteristic value assignment
  • 7. Second level characteristic value assignment
  • 8. Choose Back (Control of resulting price)
  • 9. Choose Save (Create assembly order)
  • 10. Call /nMFBF (Repetitive Manufacturing backflush)
  • 11. Enter sales order data
  • 12. Choose Save
  • 13. Call /nVL01N (Create outbound delivery)
  • 14. Select sales order
  • 15. Choose Save
  • 16. Call /nLT03 (create transfer order)
  • 17. Save transfer order
  • 18. Call /nLT12 (confirm transfer order)
  • 19. Confirm transfer
  • 20. Call /nSO01 (SAP office - inbox)
  • 21. Select workflow-item
  • 22. Start goods issue via workflow
  • 23. Call /nVF01 (create invoice)
  • 24. Choose Save invoice
  • 25. Call /nend
  • 26. Confirm log off
 

User interaction steps 2 - 24 are repeated n times (23 user interaction steps --> min. 230 sec. duration).

Business aspect:
One run corresponds to the full assemble-to-order scenario for one item.

Collapse

Cross Application Time Sheet (CATS)

The Cross Application Time Sheet (CATS) can be used by employees or personal administrators to track employee working times. Time data is recorded with information referring to orders and cost centers, for example, and can be transferred to corresponding applications and components of the SAP Business Suite.

 
Dialog Steps
  • 0. Logon
  • 1. Call transaction CAC2
  • 2. Sort employees
  • 3. Choose four employees (scroll down once)
  • 4. Choose Create time data
  • 5. Enter time data and choose Return
  • 6. Choose Save
  • 7. Choose Sort
  • 8. Select another employee
  • 9. Call help requests for cost center
  • 10. Select cost center
  • 11. Call help request for internal order
  • 12. Select internal order
  • 13. Enter new time data and choose Return
  • 14. Choose Save
  • 15. Choose Sort
  • 16. Select five employees
  • 17. Change data
  • 18. Choose Last page
  • 19. Select last line
  • 20. Select all
  • 21. Choose Delete
  • 22. Choose Save
  • 23. Log off
 

Business aspect:
One run corresponds to the processing of 80 activity reports for 5 employees

Collapse

Financial Accounting (FI)

The following table provides an overview of the business process the Financial Accounting (FI) Benchmark simulates. In this scenario, four financial documents with three line items are posted, with the line items in the fourth posting displayed. Following that, 44 open items of one debtor, including the previously posted documents, are displayed, and four are balanced. At the end of each run there are exactly 40 open items for each debtor, which serve as the basis for a new run.

 

Benchmark Results

Three-tier Internet configuration, SAP R/3 Release 2.2

Dialog Steps
  • 0. Logon
  • 1. Main screen
  • 2. Call Post Document
  • 3. Create customer item
  • 4. Create general ledger account item
  • 5. Choose Post
  • 6. Call Display document
  • 7. Enter previous posted document
  • 8. Double-click first line
  • 9. Call Customer line item display
  • 10. Enter data and choose Execute
  • 11. Select first line
  • 12. Call Post incoming payments
  • 13. Enter header data
  • 14. Choose Process open items
  • 15. Select item 5 of the list
  • 16. Scroll down to the end
  • 17. Select last item
  • 18. Deactivate all selected items
  • 19. Choose Post
  • 20. Call /nend
  • 21. Confirm log off
Collapse

Human Resources - Payroll (HR)

'In contrast to online benchmarks, the Human Resources - Payroll (HR) Benchmark is a report with variants that is run as a batch job on the basis of events. The report, called RPCALCD0, exercises the German payroll program.

 

Benchmark Results

Two-tier Internet configuration, SAP R/3 Enterprise Releases 4.6C - 4.70

 

Procedure

While the procedure for this report is complex, the following features can provide insight into its underlying business processes. Starting with the personal number and the payroll period, the report runs through these transactions in the German payroll program:

  • Basic data
  • Last payroll results
  • Capital formation
  • Company pension plan
  • Net payments/deductions and transfers
  • Final processing
 

The benchmark run has the following procedure:

  • 1. Two users log on to the system.
  • 2. The first user resets the data.
  • 3. When the high-load phase of the run has come to an end (when the first batch process has come to an end), the first user logs off.
  • 4. The second user waits until all processes have finished and then triggers the evaluation before logging off.
Collapse

Material Management (MM)

The Materials Management (MM) Benchmark takes you through a series of steps to create a purchase requisition for five materials (transaction ME51N), a purchase order for the five materials (ME21N), a goods receipt (MIGO), and an invoice (MIRO) for the purchase order.

 

Benchmark Results

Two-tier Internet configuration, SAP R/3 2.2C

 

Dialog Steps
  • 0. Logon
  • 1. Main screen
  • 2. Call /nME51N (Create purchase requisition)
  • 3. Enter data
  • 4. Choose Post
  • 5. Call /nME21N (Create purchase order)
  • 6. Enter data
  • 7. Choose Post
  • 8. Call /nMIGO (Goods receipt purchase order)
  • 9. Enter data
  • 10. Choose Execute
  • 11. Choose Post
  • 12. Call /nMIRO (Create invoice), enter company code
  • 13. Enter basic data
  • 14. Choose Payment
  • 15. Enter data
  • 16. Choose Post
  • 17. Call /nend
  • 18. Confirm log off
Collapse

Production Planning (PP)

The Production Planning (PP) Benchmark consists of the following transactions:

  • Create a production order. (CO01)
  • Change the amount on the production order, release order for production, and print order. (CO02)
  • Create two completion confirmations for the production order (milestone confirmation with back flush and final confirmation). (CO11N)
  • Post goods receipt for the order. (MB31)
  • Settle the production order. (CO02)
 

Benchmark Results

Two-tier Internet configuration, SAP R/3 Release 2.2 

 
Dialog Steps
  • 0. Logon
  • 1. Main screen
  • 2. Call Create production order
  • 3. Enter general data
  • 4. Enter data
  • 5. Choose Save
  • 6. Call Change production order
  • 7. Enter order number, choose Return
  • 8. Change data
  • 9. Select order
  • 10. Choose Functions
  • 11. Choose Release
  • 12. Choose Order
  • 13. Choose Print
  • 14. Choose OK
  • 15. Choose Save
  • 16. Call Create completion confirmation
  • 17. Enter data
  • 18. Choose Save
  • 19. Call Create completion confirmation
  • 20. Enter data
  • 21. Choose Save
  • 22. Call Create goods receipt
  • 23. Enter data
  • 24. Copy data
  • 25. Choose Save
  • 26. Call Change production order
  • 27. Choose Environment
  • 28. Choose Individual processing
  • 29. Enter data and choose execute
  • 30. Call /nend
  • 31. Confirm log off
Collapse

Sales and Distribution (SD and SD-Parallel)

The Sales and Distribution (SD) Benchmark covers a sell-from-stock scenario, which includes the creation of a customer order with five line items and the corresponding delivery with subsequent goods movement and invoicing. It consists of the following transactions:

  • Create an order with five line items. (VA01)
  • Create a delivery for this order. (VL01N)
  • Display the customer order. (VA03)
  • Change the delivery (VL02N) and post goods issue.
  • List 40 orders for one sold-to party. (VA05)
  • Create an invoice. (VF01)

Each benchmark user has his or her own master data, such as material, vendor, or customer master data to avoid data-locking situations.

Important note: On January 1, 2009, the SAP SD Benchmark was updated. Alongside the upgrade to SAP Business Suite 7 and the SAP enhancement package 4 for SAP ERP 6.0, a number of additional, necessary updates were implemented. Business changes constantly, for example, Unicode and the use of the new general ledger are now common practice for SAP customers across all industries, and the SAP standard application benchmarks need to reflect this change. The updates are transparent; that is, the steps of the benchmark scenario remain unchanged. Please be aware that these changes make the SD benchmark more resource-intensive, which has a direct impact on the benchmark results.

 

Benchmark Results - SD

 

SD-Parallel

 
SD Versus SD-Parallel
The SD-Parallel Benchmark consists of the same transactions and user interaction steps as the SD Benchmark. This means that the SD-Parallel Benchmark runs the same business processes as the SD Benchmark. The difference between the benchmarks is the technical data distribution.
Collapse
An Additional Rule for Parallel and Distributed Databases
It is generally accepted that data distribution can significantly influence the benchmark result in a parallel environment. Therefore, in May 1996, the SAP Benchmark Council redefined data distribution to establish a means to reproduce and compare results within parallel benchmarks. The additional rule is: Equally distribute the benchmark users across all database nodes for the used benchmark clients (round-robin-method).
Collapse
How to Appraise the Benchmark Results

Parallel benchmarks depend on the additional parameter "data distribution," which, by definition, does not exist in single database benchmarks. All tests show that the scalability of parallel databases significantly depends on the data distribution. When you compare SD Benchmark with SD-Parallel Benchmark results, you have to remember this difference.

Collapse
Dialog Steps
  • 0. Logon
  • 1. Main screen
  • 2. Call /nVA01 (Create customer order)
  • 3. First screen
  • 4. Second screen (with five items)
  • 5. Choose Save
  • 6. Call /nVL01N (Create a delivery)
  • 7. First screen
  • 8. Choose Save
  • 9. Call /nVA03 (Display customer order)
  • 10. Choose Enter
  • 11. Call /nVL02n (Change delivery)
  • 12. Choose [F20] (Posts goods issue)
  • 13. Call /nVA05 (List orders)
  • 14. Choose Enter
  • 15. Call /nVF01 (Create invoice)
  • 16. Choose Save
  • 17. Call /nend
  • 18. Confirm log off

User interaction steps 2 - 16 are repeated n times (15 user interaction steps --> min. 150 sec. duration).

Business aspect:
One run (user interaction steps 2 - 16) corresponds to the selling of five items.

Collapse

Benchmark Results

SAP ATO Standard Application Benchmark Results, Two-Tier Internet Configuration, R/3 Releases 4.0 - 4.6
Date of Certification
(mm/dd/yyyy)
  Technology Partner   Fully Processed Assembly Orders Per Hour   Operating System  Release   RDBMS Release   R/3 Release   Central Server   Central server memory (MB)   Certification Number
09/02/2011   Oracle   206360   Solaris 10   Oracle 11g   SAP enhancement package 4 for SAP ERP 6.0   SPARC Enterprise Server M9000, 64 processors / 256 cores / 512 threads, SPARC64 VII+, 3.00 GHz, 64 KB (D) + 64 KB (I) L1 cache per core, 12 MB L2 cache per processor,   2097152   2011033
09/02/2011   Fujitsu   206360   Solaris 10   Oracle 11g   SAP enhancement package 4 for SAP ERP 6.0   SPARC Enterprise Server M9000, 64 processors / 256 cores / 512 threads, SPARC64 VII+, 3.00 GHz, 64 KB (D) + 64 KB (I) L1 cache per core, 12 MB L2 cache per processor,   2097152   2011033
03/11/2003   Fujitsu Siemens Computers   12170   Solaris 8   Oracle 9i   4.6C   Fujitsu Siemens Computers PRIMEPOWER 900, 16-way SMP, SPARC64TM V, 1.35 GHz, 256 KB L1 cache, 2 MB L2 cache   65536   2003012
03/11/2003   Fujitsu Siemens Computers   6220   Solaris 8   Oracle 9i   4.6C   Fujitsu Siemens Computers PRIMEPOWER 900, 8-way SMP, SPARC64TM V, 1.35 GHz, 256 KB L1 cache, 2 MB L2 cache   32768   2003011
12/13/2002   HP   3090   HP-UX 11i   Oracle 9i   4.6C   hp rx5670, 4-way SMP, Itanium II, 1 GHz, 3 MB L3 cache   24576   2002069
03/22/2002   HP   3740   HP-UX 11i   Oracle 9i   4.6C   HP Server Model RP7410, 8-processors SMP, PA-RISC 8700 750 MHz, 2.25 MB L1 cache   16384   2002016
09/17/2001   HP   7000   HP-UX 11i   Oracle 8.1.7   4.6C   HP RP8400, 16-way PA-RISC 8700 750 MHz, 2.25 MB cache   32768   2001034
05/29/2001   Fujitsu Siemens   34260   Solaris 8   Oracle 8.1.7   4.6B   Fujitsu Siemens Primepower 2000, 128-processors SMP, Sparc64 560 MHz, 8 MB L2 cache   131072   2001018
04/12/2001   HP   18870   HP-UX 11.11   Oracle 8.1.6   4.6B   HP9000 Superdome Enterprise Server, 64-way SMP, PA-RISC 8600, 552 MHz   131072   2001014
02/05/2001   HP   1610   Windows 2000   SQL Server 2000   4.6B   HP NetServer LXr8500, 8-way SMP, Pentium III Xeon 700 MHz, 2 MB L2 cache   8192   2001003
12/11/2000   HP   16480   HP-UX 11.11   Oracle 8.1.6   4.6B   HP9000 Superdome Enterprise Server, 64-way SMP, PA-RISC 8600, 552 MHz   131072   2000030
11/10/2000   Bull   8570   AIX 4.3.3   DB2 UDB 7.1   4.6B   Bull Escala Model EPC 2450, 24-way SMP, RS64-IV 600 MHz, 16 MB L2 cache   32768   2000027
11/10/2000   Bull   6300   AIX 4.3.3   DB2 UDB 7.1   4.6B   Bull Escala Model EPC 2400, 24-way SMP, RS64-III 450 MHz, 8 MB L2 cache   32768   2000026
10/13/2000   IBM   8570   AIX 4.3.3   DB2 UDB 7.1   4.6B   IBM eServer pSeries 680, 24-way SMP, RS64-IV 600 MHz, 16 MB L2 cache   32768   2000025
10/13/2000   IBM   6300   AIX 4.3.3   DB2 UDB 7.1   4.6B   IBM RS/6000 Enterprise Server S80, 24-way SMP, RS64-III 450 MHz, 8 MB L2 cache   32768   2000024
03/31/2000   IBM   7700   AIX 4.3.3   DB2 UDB 6.1   4.0B   IBM RS/6000 Enterprise Server S80, 24-way SMP, RS64-III 450 MHz, 8 MB L2 cache   32768   2000008
09/13/1999   Compaq   2610   Tru64 Unix 4.0 F   Oracle 8.0.4   4.0B   AlphaServer GS 140, 8 way SMP, Alpha 21264A EV67 700 MHz, 8 MB L2 cache   16384   1999028
09/10/1999   HP   2260   HP-UX 11.0   Informix 7.30 FC7   4.0B   HP9000 N4000, 8-way SMP, PA-8500 440 MHz, 1.5 MB L1 cache   16384   1999026
06/14/1999   IBM   2390   QS/400 V4R4   DB2 UDB for AS/400 V4R4   4.0B   IBM AS/400e Model S40-2208 12-way SMP, Power PC 262 MHz, 8 MB L2 cache   6144   1999013
03/12/1999   Sun   2020   Sun Solaris 2.6   Informix 7.30 UC7   4.0B   Sun 6000, Model E 6000, 24 way SMP, UltraSparc II 250 MHz, 1MB L2 cache   16384   1999006
12/18/1998   Compaq   780   Digital Unix 4.0 D   Oracle 8.0.4   4.0B   Compaq Alpha Server 4100 5/600, 4 way SMP, 600 MHz, 4MB L2 cache   8192   1998040
SAP MM Standard Application Benchmark Results, Two-Tier Internet Configuration, R/3 Release 2.2
Date of Certification (mm/yyyy)   Technology Partner   Number of Benchmark Users   Benchmark Type   Average Dialog Response Time (sec)   Operating System - Release   RDBMS Release   R/3 Release   Central Server   Central Server Memory (MB)
03/1995   Digital   360   MM   0.65   OSF/1 3.2   Oracle 7.1.4   2.2 C   DEC 8400 TurboLaser, 8-way SMP   8,192
SAP PP Standard Application Benchmark Results, Two-Tier Internet Configuration, R/3 Release 2.2
Date of Certification (mm/yyyy)   Technology Partner   Number of Benchmark Users   Benchmark Type   Average Dialog Response Time (sec)   Operating System - Release   RDBMS Release   R/3 Release   Central Server   Central Server Memory (MB)
03/1995   Digital   180   PP   2.00   OSF/1 3.2   Oracle 7.1.4   2.2 C   DEC 8400 TurboLaser, 8-way SMP   8,192
SAP SD Parallel Standard Application Benchmark Results - With Round Robin
Date of Certification
(mm/dd/yyyy)
  Technology Partner   Number of Benchmark Users   Benchmark Type   Average Dialog Response Time (sec)   Dialog Steps Per Hour   SAPS   Line Items Per Hour   Operating System - Release   RDBMS Release   R/3 Release   Database Server   Database Server Memory (MB)   Number & Amount of Application Servers   Certification Number
10/03/2011   Oracle   49860   SD   0.91   16445000   274080   5481670   Solaris 10   Oracle 11g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0   2 x Sun Fire X4800 M2, 8 processors / 80 cores / 160 threads, Intel Xeon Processor E7-8870, 2.40 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 30 MB L3 cache per processor   2 x 524288   ran on database servers   2011040
10/03/2011   Oracle   94736   SD   0.41   32763000   546050   10921000   Solaris 10   Oracle 11g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0   4 x Sun Fire X4800 M2, 8 processors / 80 cores / 160 threads, Intel Xeon Processor E7-8870, 2.40 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 30 MB L3 cache per processor   4 x 524288   ran on database servers   2011039
10/03/2011   Oracle   137904   SD   0.81   45928000   765470   15309330   Solaris 10   Oracle 11g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0   6 x Sun Fire X4800 M2, 8 processors / 80 cores / 160 threads, Intel Xeon Processor E7-8870, 2.40 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 30 MB L3 cache per processor   6 x 524288   ran on database servers   2011038
10/03/2011   Oracle   180000   SD   0.63   60983000   1016380   20327670   Solaris 10   Oracle 11g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0   8 x Sun Fire X4800 M2, 8 processors / 80 cores / 160 threads, Intel Xeon Processor E7-8870, 2.40 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 30 MB L3 cache per processor   8 x 524288   ran on database servers   2011037
9/12/2011   Oracle   134080   SD   0.87   44415000   740250   14805000   Solaris 10   Oracle 11g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0   6 x Sun Fire X4800 M2, 8 processors / 80 cores / 160 threads, Intel Xeon Processor E7-8870, 2.40 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 30 MB L3 cache per processor   6 x 524288   ran on database servers   2011036
9/20/2010   Oracle   40000   SD   0.86   13261000   221020   4420330   Solaris 10   Oracle 11g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0   4 x Oracle/Sun Fire X4470, 4 processors / 32 cores / 64 threads, Intel Xeon Processor X7560, 2.26 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 24 MB L3 cache per processor   1 x 262144   ran on database server   2010039
6/28/2010   Oracle   21000   SD   0.93   6918000   115300   2306000   Solaris 10   Oracle 11g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0   2 x Oracle/Sun Fire X4470, 4 processors / 32 cores / 64 threads, Intel Xeon Processor X7560, 2.26 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 24 MB L3 cache per processor   1 x 262144   ran on database server   2010029
10/12/2009   Sun Microsystems   3800   SD   0.99   1245000   20750   415000   Solaris 10   Oracle 10g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0 (Unicode)   1 x Sun Blade X6270, 2 processors / 8 cores / 16 threads, Intel Xeon Processor X5570, 2.93 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 8 MB L3 cache per processor   1 x 49152   ran on database server   2009039
10/12/2009   Sun Microsystems   7220   SD   0.99   2365000   39420   788330   Solaris 10   Oracle 10g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0 (Unicode)   2 x Sun Blade X6270, 2 processors / 8 cores / 16 threads, Intel Xeon Processor X5570, 2.93 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 8 MB L3 cache per processor,   2 x 49152   ran on database server   2009040
10/12/2009   Sun Microsystems   13718   SD   0.86   4546000   75770   1515330   Solaris 10   Oracle 10g Real Application Clusters (RAC)   SAP enhancement package 4 for SAP ERP 6.0 (Unicode)   4 x Sun Blade X6270, 2 processors / 8 cores / 16 threads, Intel Xeon Processor X5570, 2.93 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 8 MB L3 cache per processor,   4 x 49152   ran on database server   2009041
09/22/2008   HP   4325   SD   1.96   1302000   21700   434000   HP-UX 11i v3   Oracle 10g Real Application Clusters (RAC)   6.0 (2005)   4 x HP Integrity BL860C, 2 processors / 4 cores / 8 threads, Dual-Core Intel Itanium Processor 9140M, 1.66 GHz, 32 KB L1 cache, 1.25 MB L2 cache, 9 MB L3 cache per core   4 x 24576   ran on database server   2008054
09/22/2008   HP   2220   SD   1.94   669000   11150   223000   HP-UX 11i v3   Oracle 10g Real Application Clusters (RAC)   6.0 (2005)   2 x HP Integrity BL860C, 2 processors / 4 cores / 8 threads, Dual-Core Intel Itanium Processor 9140M, 1.66 GHz, 32 KB L1 cache, 1.25 MB L2 cache, 9 MB L3 cache per core   2 x 24576   ran on database server   2008053
03.25.2008   IBM   37040   SD   1.86   11247000   187450   3749000   AIX 5L Version 5.3   Oracle 10g Real Application Clusters (RAC)   6.0 (2005)   5 x IBM System p 570, 8 processors / 16 cores / 32 threads, POWER6 4.7 GHz, 128 KB L1 cache and 4 MB L2 cache per core, 32 MB L3 cache per processor   5 x 131072   ran on database server   2008013
03.25.2008   IBM   30016   SD   1.86   9108000   151800   3036000   AIX 5L Version 5.3   Oracle 10g Real Application Clusters (RAC)   6.0 (2005)   4 x IBM System p 570, 8 processors / 16 cores / 32 threads, POWER6 4.7 GHz, 128 KB L1 cache and 4 MB L2 cache per core, 32 MB L3 cache per processor   4 x 131072   ran on database server   2008012
03.25.2008   IBM   22416   SD   1.94   6757000   112620   2252330   AIX 5L Version 5.3   Oracle 10g Real Application Clusters (RAC)   6.0 (2005)   3 x IBM System p 570, 8 processors / 16 cores / 32 threads, POWER6 4.7 GHz, 128 KB L1 cache and 4 MB L2 cache per core, 32 MB L3 cache per processor   3 x 131072   ran on database server   2008011
03.25.2008   IBM   15520   SD   1.94   4678000   77970   1559330   AIX 5L Version 5.3   Oracle 10g Real Application Clusters (RAC)   6.0 (2005)   2 x IBM System p 570, 8 processors / 16 cores / 32 threads, POWER6 4.7 GHz, 128 KB L1 cache and 4 MB L2 cache per core, 32 MB L3 cache per processor   2 x 131072   ran on database server   2008010
11/9/2007   IBM   36000   SD   1.76   11021000   183680   3673670   AIX 5L Version 5.3   Oracle 10g Real Application Clusters   6.0 (2005)   5 x IBM System p 570, 8 processors / 16 cores / 32 threads, POWER6, 4.7 GHz, 128 KB L1 cache and 4 MB L2 cache per core, 32 MB L3 cache per processor   5 x 131072   ran on database server   2007066
7/1/2005   IBM   2400   SD   1.95   723000   12050   241000   AIX 5.3   Oracle 9i Real Application Clusters   4.7   2 x IBM eServer p5 Model 570, 4-way SMP, POWER5, 1.9 GHz, 32 KB(D) + 64 KB(I) L1 cache per processor, 1.92 MB L2 cache and 36 MB L3 cache per 2 processors   2 x 32768   ran on database server   2005033
6/29/2004   Dell   1350   SD   1.97   406000   6770   135330   Redhat Enterprise Linux 3   Oracle 9i Real Application Clusters   4.7   2 x Dell PowerEdge Model 6650, 4-way SMP, Intel XEON MP, 3.0 GHz, 20 KB L1 cache, 512 KB L2 cache, 4 MB L3 cache   2 x 8192   ran on database server   2004038
06/03/2002   HP   12,000   SD   1.92   3,625,000   60,420   1,208,330   HP Tru64 Unix V5.1A   Oracle 9i Real Application Clusters   4.6 C   4 x AlphaServer ES45 Model 2, 4-way SMP, Alpha EV6.8CB (21264C), 8MB L2C   4 x 32,768   65 x AlphaServer ES45 Model 2, 4-way SMP, Alpha EV6.8CB (21264C)   2002031
06/03/2002   HP   6,580   SD   1.81   2,005,000   33,420   668,330   HP Tru64 Unix V5.1A   Oracle 9i Real Application Clusters   4.6 C   2 x AlphaServer ES45 Model 2, 4-way SMP, Alpha EV6.8CB (21264C), 8MB L2C   2 x 32,768   33 x AlphaServer ES45 Model 2, 4-way SMP, Alpha EV6.8CB (21264C)   2002030
06/03/2002   HP   3,640   SD   0.81   1,212,000   20,200   404,000   HP Tru64 Unix V5.1A   Oracle 9i Real Application Clusters   4.6 C   2 x AlphaServer ES45 Model 2, 4-way SMP, Alpha EV6.8CB (21264C), 8MB L2C (one active, one passive)   2 x 32,768   17 x AlphaServer ES45 Model 2, 4-way SMP, Alpha EV6.8CB (21264C)   2002029
09/22/2000   Amdahl   1,000   SD   1.24   320,000   5,330   106,670   DB: OS/390 V2.8, Apps: Windows NT 4.0   DB2 UDB for OS/390 Version 6.1   4.6 B   Model GS2108E, 10-way SMP, CMOS Based Processor, 2MB L2C   2 x 1,024   13 x GP5-L895LR, 4-processors SMP, Pentium III Xeon 550   2000023
07/23/1998   IBM   8,000   SD   1.58   2,487,000   41,450   829,000   OS/390 V1R3   DB2 for OS/390 Version 5.1   3.1H   3 x IBM S/390, 9672-RY5 G4 CMOS, 10 Proc., 2GB cntrl, 1GB expand.   3 x 2,048   55x RISC System/6000, 550 nodes: 54 dia/upd, 1 msg/enq   1998017
06/11/1998   IBM   6,900   SD   1.69   2,128,000   35,470   709,000   OS/390 V1R3   DB2 for OS/390 Version 5.1   3.1H   3 x IBM S/390, 9672-RY5 G4 CMOS, 10 Proc., 2GB cntrl, 1GB expand.   3 x 2,048   49 x RISC System/6000, 550 nodes: 48 dia/upd, 1 msg/enq   1998011
05/13/1997   IBM   2,570   SD   1.16   819,000   13,650   273,000   OS/390 V1R3   DB2 for OS/390 Version 5   3.0 E (3.0 F kernel)   3 database nodes each: IBM 9672 S/390 RX3 CMOS CISC 83.3 MHz, 10 processors   3 x 2,048   RS/6000 SP, 104 nodes: 102 dia/ upd, 1 enque, 1 message   1997016
05/13/1997   IBM   1,750   SD   1.29   565,000   9,417   188,000   OS/390 V1R3   DB2 for OS/390 Version 5   3.0 E (3.0 F kernel)   2 database nodes each: IBM 9672 S/390 RX3 CMOS CISC 83.3 MHz, 10 processors   2 x 2,048   RS/6000 SP, 56 nodes: 54 dia/ upd, 1 enque, 1 message   1997015
05/13/1997   IBM   3,400   SD   1.50   1,065,000   17,750   355,000   OS/390 V1R3   DB2 for OS/390 Version 5   3.0 E (3.0 F kernel)   4 database nodes each: IBM 9672 S/390 RX3 CMOS CISC 83.3 MHz, 10 processors   4 x 2,048   RS/6000 SP, 143 nodes: 141 dia/ upd, 1 enque, 1 message   1997014
03/12/1997   IBM   1,700   SD   0.69   573,000   9,559   191,000   AIX 4.1.4   Oracle Parallel Server 7.3.2   3.0 D   RS/6000 SP, 5 database nodes each 8-way SMP Power PC 604   5 x 2,048   RS/6000 SP, 104 nodes: 103 dia/ upd, 1 enque / message   1997004
03/12/1997   IBM   1,050   SD   0.67   354,000   5,900   118,000   AIX 4.1.4   Oracle Parallel Server 7.3.2   3.0 D   RS/6000 SP, 3 database nodes each 8-way SMP Power PC 604   3 x 2,048   RS/6000 SP, 67 nodes: 66 dia/ upd, 1 enque / message   1997003
03/12/1997   IBM   760   SD   0.68   256,000   4,267   85,000   AIX 4.1.4   Oracle Parallel Server 7.3.2   3.0 D   RS/6000 SP, 2 database nodes each 8-way SMP Power PC 604   2 x 2,048   RS/6000 SP, 54 nodes: 53 dia/ upd, 1 enque / message   1997001
12/11/1996   IBM   1,520   SD   0.74   510,000   8,500   170,000   AIX 4.1.4   Oracle Parallel Server 7.3.2   3.0 D   RS/6000 SP, 5 database nodes each 8-way SMP Power PC 604   5 x 2,048   RS/6000 SP, 113 nodes: 111 dia/ upd, 1 enque, 1 message   1996023
SAP SD Parallel Standard Application Benchmark Results - Without Round Robin
Date of Certification
(mm/dd/yyy)
  Technology Partner   Number of Benchmark Users   Benchmark Type   Average Dialog Response Time (sec)   Dialog Steps Per Hour   SAPS   Line Items Per Hour   Operating System - Release   RDBMS Release   R/3 Release   Database Server   Database Server Memory (MB)   Number & Amount of Application Servers
06/30/1995   IBM   800   SD   1.00   265,536   4,426   87,000   AIX 3.2.5   Oracle Parallel Server 7.1   2.2 D   RS/6000 SP2, 8 database nodes   2,048   SP2, 41 nodes (32 dia, 8 upd, 1 enque)
Back to top