1 / 16

Performance, Scalability & Benchmarking of mySAP

Performance, Scalability & Benchmarking of mySAP.com. Bernd F. Lober SAP AG. Plant Personnel. Customer Service Rep. Create Production Orders. Production Order. Accept Customer Order. Explode Bill-of- Material. Release Production Orders. Build Products. Reserve Material.

vivaa
Download Presentation

Performance, Scalability & Benchmarking of mySAP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Performance, Scalability & Benchmarking of mySAP.com Bernd F. LoberSAP AG

  2. Plant Personnel Customer Service Rep Create Production Orders Production Order Accept Customer Order Explode Bill-of- Material Release Production Orders Build Products Reserve Material Schedule Production Customer Order Material Task Part Confirm Delivery Multi-tier Internet Architecture Load Layer 2-tier 3-tier Multi-tier Internet Architecture 10-20% Presentation Services Presentation Services Web Browser User Dialog: Graphical information processing Presentation Web Server Web Server Handling Internet access 5-10% Internet Server Internet Server Processing Internet Transactions Internet Application Services Processing application logic: System Management Transaction Monitoring Application Services 60-70% Application Database Services Database Services 10-20% Information Storage Database Backup Database

  3. Vertical Scalability • Multi-tier Internet architecture • One-tier: Laptop Demo System • Two-tier: Central Installation (database and application part on one physical server), multiple presentation servers • Three-tier: One database server, multiple application servers and multiple presentation servers • Multi-tier: One database server, multiple application servers multiple presentation servers, mutiple Internet Transaction Server and multiple Web servers

  4. Horizontal Scalability • Presentation Layer • 26,000 very active users connected to one database have been tested • Internet Transaction Server and Web Server • More than 100 hits /sec • Application Layer • Up to 161 application servers have been tested successfully • The highest number of physical application servers at customer installations is less than 30 • Database Layer • Scalability through SMP architecture of the database server • More than 120 CPUs and more than 10 TB Database size • Scalability through parallel databases • Scalability through Components

  5. SAP Standard Application Benchmarks mySAP Supply Chain Management mySAP Human Resources Cross Application Time Sheets - CATS Materials Management - MM Payroll Sales & Distribution - SD Production Planning - PP mySAP Financials Warehouse Management - WM Assemble - To - Order - ATO Financial Accounting - FI Advanced Planning and Optimizing - APO Industry Solutions mySAP Product Lifecycle Management Retail Project System - PS Banking - Bank Customer Accounts - BCA Utilities - Customer Care and Service - CCS mySAP Business Intelligence mySAP Customer Relationship Mgmt Business Information Warehouse - BW Internet Sales Customer Interaction Center E-commerce Online Store

  6. CPU Utilization of Different Servers

  7. Published Results for SD Benchmarks (Two-tier Client/Server Configuration) 1995 1996 1993 1994 1997 2000 2002 2003 1998 1999 2001 9000 Rel. 4.6C 128-wayServer 8000 7800 7000 Number of SD Benchmark users 6000 5000 Rel. 4.6C 76-wayServer 4100 4000 Rel. 4.0 B 64-wayServer 3000 3000 Rel. 2.2 C 8-way Server Rel. 3.0 E 64-way Server 2000 1708 Rel. 2.2 G 24-way Server 1410 Rel. 4.0 B 24-wayServer 1000 600 300 0 Two-tier Internet Architecture

  8. Published Results for SD Benchmarks (Highest Number of Users) 1996 1993 1994 1995 1997 2000 1998 1999 2001 2002 30000 26000 25560 25000 Number of SD Benchmark users 24000 23000 20000 19360 16440 15000 14400 10000 6750 6030 5000 5320 3700 2900 600 1400 2000 900 300 1700 120 0 Three-tier Internet Architecture

  9. Key Figures for the 26,000 SD User Benchmark

  10. Published Results for SD Benchmarks (Highest Number of Line Items) 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 3000000 2606000 2573330 2500000 2411330 2353670 Fully business-processed order line items per hour 2000000 1954670 1669000 1575000 1500000 1000000 678000 607000 534000 380000 500000 230000 299000 115000 175000 33000 12000 90000 0 Three-tier Internet Architecture

  11. Published Results for the ATO Benchmark (3-Tier) 2002 1998 1999 2000 2001 160000 144090 140000 Highest Number of Assembly Orders 130570 120000 100000 80000 60000 54220 40000 22610 20000 9130 0

  12. Published Result for the APO Benchmark (Demand Planning) 2000 2001 2002 2003 140000 129871 120000 100000 79611 80000 53199 60000 40000 20000 0 Number of Planned Characteristic Combinations at Aggregated Level Per Hour

  13. www.sap.com/benchmark

  14. "Load Factors" based on the SAP Standard Application Benchmarks Version 4.6 - Example 7,00 Rel. CPU-Usage / Dialogstep 6,00 Platform & Release dependent 5,00 79% 4,00 3,00 80% 2,00 81% 8% Database 77% 1,00 88% 74% 9% 10% 13% 6% 10% 11% Update 9% 11% 6% 16% 11% 0,00 FI WM MM SD PP ATO Dialog SAP Business Component

  15. Summary • Proven Scalability - with enough potential for future growth • mySAP.com exploits the latest available components Useful addresses: http://www.sap.com/benchmarkhttp://service.sap.com/performance http://service.sap.com/sizing

  16. Questions And Answers

More Related