HW Deployment DIAGRAMS - Version 6 4

5/22/2018 HW Deployment DIAGRAMS PDF FILE - Version 6 4

1/16

SAP Software on WindowsHardware Configurations for Optimal PerformanceDiagrams to acco mpany Note 1612283

Appl ies to :

SAP Netweaver and Stand Alone Components running on Windows

SummaryIntroduction: SAP Note 1612283 contains a detailed and in depth explanation of SAP Software running on Windows and Intel servers.These diagrams are designed to illustrate to customers and partners the concepts explained in Note 1612283.Note 1612283 should be read carefully before reviewing this document.

Author (s):Cameron Gardiner, Microsoft CorporationContact Person for questions and comments on this article:[email protected]

Reviewer(s):Karl-Heinz Hochmuth, SAP AGBernd Lober, SAP AGPeter Simon, SAP AGJrgen Thomas, Microsoft Corporation

Company: SAP AGCreated on:September 2012


2/16

Configuration 1 Notes:

A single SAP instance on a powerful modern Intel or AMD server cannot leverage the CPU and memory resources available. Increasing the number of work

processes on a single instance above ~50 will not lead to a proportionate increase in throughput. Installing additional instances is recommended.

Physical Server Configuration

2 socket Intel E5 32 threads / 16 cores / 2 NUMA nodes / 256GB RAM (128GB RAM per NUMA node)

10 Gigabit Network

PHYS_MEMSIZE is not set therefore SAP defaults to the total amount of RAM (256GB)

Approximately 50 work processes. If more work processes are needed it is best to install another instance

Virtual Machine Configuration

Virtual machine configuration can be up to the total number of vCPU and vRAM or Hyper-Visor limit. Virtual Machines configuration must follow the

requirements of SAP Notes such as no overcommit for production systems, adequate network cards and enhanced monitoring

10 Gigabit Network with SRIOv is recommended to improve network performance

PHYS_MEMSIZE should be set on Virtual Machines in case Dynamic Memory feature is used

Approximately 50 work processes will give best performance. If more work processes are needed it is best to install another instance


3/16


4/16


It is recommended to consolidate multiple SAP application servers onto one powerful 2 socket server. Customers have successfully run 5-8 SAP instances on one

2 socket server. Real customer deployments have indicated that the limiting factor is RAM rather than CPU resources

Physical Server Configuration2 socket AMD 32 thread / 32 core / 2 NUMA nodes / 256GB RAM (128GB RAM per NUMA node)

10 Gigabit Network

PHYS_MEMSIZE can be set to either a fixed amount of RAM or a percentage value. Example on a server with 8 instances and 256GB RAM 32GB can be allocated

to each ABAP instance. Alternatively the value 12.5% could be used for the profile parameter PHYS_MEMSIZE

Approximately 50 work processes per each ABAP instance. Performance testing has shown many smaller ABAP instances deliver better throughput than a few

large instances. If more work processes are needed it is best to install another instance


Virtual machine configuration can be up to the total number of vCPU and vRAM or hypervisor limit. Virtual Machines configuration must follow the requirements

of SAP Notes such as no overcommit for production systems, adequate network cards and enhanced monitoring



Approximately 50 work processes will give best performance. If more work processes are needed it is best to install another instance


5/16


6/16


Modern 2 socket servers deliver more than 40,000 SAPS. The total SAPS requirement for some customers is less than 40,000 SAPS. In such cases customers may

consolidate both DBMS and run 3-5 SAP instances on one 2 socket server. Real customer deployments have indicated that the limiting factor is RAM rather than

CPU or IO resources. Intel and AMD CPU are very powerful. Large DBMS data caches reduce physical IO to disk dramatically (in combination with DBMS

compression). IO performance can be scaled up by adding HBA, FCoE or 10 Gigabit NIC (for iSCSI)


1. 2 socket Intel E5 32 threads / 16 cores / 2 NUMA nodes / 384GB RAM (192GB RAM per NUMA node)2. 10 Gigabit Network

3. DBMS software should be configured to use a large data cache to reduce physical disk IO. Recommended values are 96GB, 128GB or more. DBMS

software is NUMA aware and can efficiently run across NUMA nodes.

4. DBMS software should be configured to use DB compression to further improve the DBMS cache hit ratio. Some databases such as SQL Server and

Sybase systems compress all tables and indexes by default. Consult the relevant SAP Notes discussing compression for each DBMS.

5. DBMS compression ratios of 40% to 85% have been observed on customer systems. If a 3TB system were compressed to 1TB (66% saving) and the

DBMS cache size set to 256GB there would be very minimal physical disk IO. Analysis of customer systems has shown when the DBMS cache size is more

than 25% of DB size in combination with compression very little (if any) physical disk READ IO will occur.

6. PHYS_MEMSIZE of all SAP ABAP instances, HEAP of all SAP Java instances and the total memory consumed by all DBMS software (data cache and any

other DBMS system type caches) should be less than the total physical memory of the server.

7. PHYS_MEMSIZE can be set to either a fixed a mount of RAM or a percentage value.

Example: A single physical server with 384GB of RAM has three separate DBMS running with a total of 176GB of RAM allocated to DBMS software (128GB +

16GB + 32GB). The single physical server has four SAP instances each with a PHYS_MEMSIZE of 32GB. The total SAP memory is at least 128GB. In total the

DBMS + SAP memory is 304GB. The remaining 80GB of RAM can be used in case another instance or additional DBMS needs to be added or if the SAP systems

have inefficient custom ABAP code that consumes a lot of extended memory.



Configuration and administration of multiple SAP application servers running on one or more physical or virtual hosts is greatly simplified by placing all profile

parameters into the default profile. This ensures identical configuration of instances, improves the operation of the SAP Logon Load Balancing mechanism and

eliminates complex configuration and administration.


Virtual machine configuration can be up to the total number of vCPU and vRAM or Hyper-Visor limit. Virtual Machines configuration must follow the




It is not recommended to use Dynamic Memory in conjunction with automatic DBMS memory management features.

Approximately 50 work processes


7/16

Conf ig 4. Multi -SID DBMS + ASCS Cluster with SAP Multip le SAP

Appl ication Server on Physical Server or Vir tual Machine2 Socket Intel SandyBridge

CPU 32 thread / 16 core384GB RAM 2 NUMA Nodes10Gigabit NIC Server LAN

1Gigabit NIC User LAN

ECC DBMS Instance 1DBMS Max Memory = fixedamount (for SQL Server leave setto AUTO)

Solman DBMS Instance 2DBMS Max Memory = fixedamount (for SQL Server leave setto AUTO)

CRM DBMS Instance 3DBMS Max Memory = fixedamount (for SQL Server leave set

to AUTO)

2 Socket Intel SandyBridge



BW DBMS Instance 4DBMS Max Memory = fixedamount (for SQL Server leave setto AUTO)

EP DBMS Instance 5DBMS Max Memory = fixedamount (for SQL Server leave set

to AUTO)

SRM DBMS Instance 6DBMS Max Memory = fixedamount (for SQL Server leave setto AUTO)




SCM DBMS Instance 7DBMS Max Memory = fixedamount (for SQL Server leave setto AUTO)

BusObj DBMS Instance 8DBMS Max Memory = fixedamount (for SQL Server leave set

to AUTO)

BI Java DBMS Instance 9DBMS Max Memory = fixedamount (for SQL Server leave setto AUTO)

Central Services ECCvHostname =

SAP System Number = 00

Central Services SolmanvHostname =

SAP System Number = 01 ABAP/02 Java

Central Services CRMvHostname =


Central Services BWv Hostname =


Central Services EPv Hostname =


Central Services SRMv Hostname =


Central Services SCMvHostname=


Central Services BI JavavHostname=





ABAP Inst ance 1ECC App Server 1

SAP System Number 00

PHYS_MEMSIZE = 32000

ABAP Inst ance 2ECC App Server 5



ABAP Inst ance 3BW App Server 1



ABAP Inst ance 4CRMAppServer1



ABAP Inst ance 5SRM App Server 1



ABAP Inst ance 6Solman App Server 1



JVM Heap = 2048

Java Instance 7EP App Server 1


JVM Heap = 2048

ABAP Inst ance 8SCM App Server 1






ABAP Instan ce 1ECC App Server 2



ABAP Instan ce 2ECC App Server 6



ABAP Instan ce 3BW App Server 2



ABAP Instan ce 4CRM App Server 2



ABAP Instan ce 5SRMAppServer2



ABAP Instan ce 6SolmanAppServer2



J VMHeap=2048



J VMHeap=2048

ABAP Instan ce 8SCMAppServer2






ABAP Instanc e 1ECC App Server 3



ABAP Instanc e 2ECC App Server 7



ABAP Instanc e 3BW App Server 3



ABAP Instanc e 4CRM App Server 3



ABAP Instanc e 5SRM App Server 3



ABAP Instanc e 6BI JAVA App Server 1


J VMHeap= 2048



J VMHeap= 2048

ABAP Instanc e 8SCM App Server 3






ABAP Insta nce 1ECC App Server 4



ABAP Insta nce 2ECC App Server 8



ABAP Insta nce 3BW App Server 4



ABAP Insta nce 4CRM App Server 4



ABAP Insta nce 5SRMAppServer4



ABAP Insta nce 6BI JAVA App Server 2



J VMHeap=2048



J VMHeap=2048

ABAP Insta nce 8SCMAppServer4



Management Station VirtualMachine(s)1 vCPU8GB vRAMHostname = managevm1


8/16


2 socket servers running in 3 tier configuration can deliver more than 200,000 SAPS for a single SAP component and more than 600,000 SAPS for an entire

production environment.

Approximately 20% or less of the SAPS of a system are consumed by the database and more than 80% can be scaled out on the application server layer.

Therefore a 1:4 ratio between DB and application server resources is normal. Experience has shown capacity can be scaled very effectively by adding application

servers. The bottleneck is typically not the DBMS servers. 10 Gigabit network and a separate dedicated internal SAP application server DBMS network is

mandatory for large configurations.


DBMS Server

1. 2 socket Intel E5 32 threads / 16 cores / 2 NUMA nodes / 384GB RAM (192GB RAM per NUMA node)

2. 10 Gigabit Network for SAP application server to DBMS server communication. A separate 1 Gigabit network for user traffic








6. Analysis of customer systems with very large DBMS cache sizes have shown almost zero physical read IO 6-12 hours after a system has been restarted.

Physical write will occur as most DBMS use write-ahead logging.

7. Some DBMS have fully automatic memory allocation. In such cases the DBMS can be set to auto and use memory as needed (eg. SQL Server). Other

DBMS software will require configuration of fixed amounts of buf fer cache for each system

8. Some DBMS software requires manual configuration to enable NUMA and Large Memory Page Sizes. Consult the DBMS vendor and/or hardware

vendors best practice document for large scale up deployments

SAP application servers

1. 4 to 12 physical servers 2 socket Intel E5 32 threads / 16 cores / 2 NUMA nodes / 384GB RAM (192GB RAM per NUMA node)2. 10 Gigabit Network

3. PHYS_MEMSIZE of all SAP ABAP instances and HEAP of all SAP Java instances should be less than the total physical memory of the server.4. PHYS_MEMSIZE can be set to either a fixed a mount of RAM or a percentage value.

Example:

A DBMS server with 384GB RAM is running DBMS software in a 3 node cluster. DBMS can run on any one of the 3 nodes.

A single physical server with 384GB of RAM has SAP instances each with a PHYS_MEMSIZE of 32GB plus a Java Instance with a HEAP size of 2GB. The total SAP

memory is at least 224GB. The remaining unused RAM can be used in case another instance needs to be added or if the SAP systems have inefficient custom

ABAP code that consumes a lot of extended memory.


9/16







Virtual machine configuration can be up to the total number of vCPU and vRAM or Hyper-Visor limit. Virtual Machines configuration must follow therequirements of SAP Notes such as no overcommit for production systems, adequate network cards and enhanced monitoring



It is not recommended to use Dynamic Memory in conjunction with automatic DBMS memory management features.

Cluster Configuration:

ASCS in 2 node cluster. The ASCS and ERS consume very little CPU, memory, network and IO. The impact of the ASCS on the sizing of the DBMS cluster is

negligible. Review the SAP Installation Guide for more information on Windows Clustering and Multi-SID clustering

Most DBMS software can run on more than 2 nodes. Example: Windows 2012 & SQL Server 2012 supports 64 nodes

Multi-SID clusters generally require the use of mount points otherwise there will be insufficient drive letters.

Notes 1634991 - How to install an ASCS or SCS instance on more than 2 cluster nodes?

1678705 - Installation scenarios for a standalone ASCS instance


10/16

Config 5. Multi -SID DBMS Cluster, Separate SCS Cluster with SAP Mult iple SAP

Appl ication Server on Physical Server or Vir tual Machine2 Socket Intel SandyBridge

CPU 32 thread / 16 core

384GB RAM 2 NUMA Nodes10Gigabit NIC Server LAN


ECC DBMS Instance 1

DBMS Max Memory = fixedamount (for SQL Server leave

set to AUTO)

Solman DBMS Instance 2

DBMS Max Memory = fixed

amount (for SQL Server leave

set to AUTO)

CRM DBMS Instance 3DBMS Max Memory = fixed

amount (for SQL Server leave

set to AUTO)





BW DBMS Instance 4

DBMS Max Memory = fixedamount (for SQL Server leave set

to AUTO)

EP DBMS Instance 5

DBMS Max Memory = fixed

amount (for SQL Server leave setto AUTO)

SRM DBMS Instance 6


to AUTO)



384GB RAM 2 NUMA N odes10Gigabit NIC Server LAN


SCM DBMS Instance 7


to AUTO)

BusObj DBMS Instance 8


to AUTO)

BI Java DBMS Instance 9DBMS Max Memory = fixed

amount (for SQL Server leave set

to AUTO)

Virtual Machine 18vCPU32GB vRAMHostname= vmhost1

Central Services ECCvHostname =


Central Services SolmanvHostname =SAP System Number = 01 ABAP/02 Java

Central ServicesCRMvHostname =


Virtual Machine 28 vCPU32GB vRAMHostname= vmhost1

Central Services BWvHostname =SAP System Number = 04

Central Services EPvHostname =SAP System Number = 05

Central Services SRMvHostname =


Central Services SCMvHostname =SAP System Number = 07

Central Services BI JavavHostname =


Management Station Virtual

Machine(s)

1 vCPU

8GB vRAM

Hostname = managevm1





ABAP Ins tance 1ECC App Server 1SAP System Number 00PHYS_MEMSIZE = 32000

ABAP Ins tance 2ECC App Server 5

SAP System Number 01PHYS_MEMSIZE = 32000

ABAP Ins tance 3BW App Server 1SAP System Number 02PHYS_MEMSIZE = 32000

ABAP Ins tance 4CRM App Server 1SAP System Number 03PHYS_MEMSIZE = 32000

ABAP Ins tance 5SRM App Server 1SAP System Number 04PHYS_MEMSIZE = 32000

ABAP Ins tance 6Solman App Server 1SAP System Number 05

PHYS_MEMSIZE = 32000JVMHeap=2048

Java Instance 7EP App Server 1SAP System Number 06JVMHeap=2048

ABAP Ins tance 8SCM App Server 1SAP System Number 07PHYS_MEMSIZE = 32000











ABAP Ins tance 6SolmanAppServer2SAP System Number 05

PHYS_MEMSIZE = 32000JVMHeap=2048





384GB RAM 2 NUMA N odes10Gigabit NIC Server LAN








ABAP Ins tance 6BI JAVA App Server 1SAP System Number 05

JVMHeap=2048







ABAP In stance 1ECC App Server 4SAP System Number 00PHYS_MEMSIZE = 32000

ABAP In stance 2ECC App Server 8


ABAP In stance 3BW App Server 4SAP System Number 02PHYS_MEMSIZE = 32000

ABAP In stance 4CRM App Server 4SAP System Number 03PHYS_MEMSIZE = 32000

ABAP In stance 5SRM App Server 4SAP System Number 04PHYS_MEMSIZE = 32000

ABAP In stance 6BI JAVA App Server 2SAP System Number 05

PHYS_MEMSIZE = 32000JVMHeap= 2048

Java Instance 7EP App Server 4SAP System Number 06JVMHeap= 2048

ABAP In stance 8SCM App Server 4SAP System Number 07PHYS_MEMSIZE = 32000


11/16


2 socket servers running in 3 tier configuration can deliver more than 200,000 SAPS for a single SAP component and more than 600,000 SAPS for an entire

production environment.


Therefore a 1:4 ratio between DB and application server resources is normal. Experience has shown capacity can be scaled very effectively by adding application

servers. The bottleneck is typically not the DBMS servers. 10 Gigabit network and a separate dedicated internal SAP application server DBMS network is

mandatory for large configurations.


DBMS Server

1. 2 socket Intel E5 32 threads / 16 cores / 2 NUMA nodes / 384GB RAM (192GB RAM per NUMA node)










Physical write will occur as most DBMS use write ahead logging.

7. Some DBMS have fully automatic memory allocation. In such cases the DBMS can be set to auto and use memory as needed (eg. SQL Server). Other

DBMS software will require configuration of fixed amounts of buf fer cache for each system

8. Some DBMS software requires manual configuration to enable NUMA and Large Memory Page Sizes. Consult the DBMS vendor and/or hardware

vendors best practice document for large scale up deployments.


1. 4 to 12 physical servers 2 socket Intel E5 32 threads / 16 cores / 2 NUMA nodes / 384GB RAM (192GB RAM per NUMA node)2. 10 Gigabit Network

3. PHYS_MEMSIZE of all SAP ABAP instances and HEAP of all SAP Java instances should be less than the total physical memory of the server.4. PHYS_MEMSIZE can be set to either a fixed a mount of RAM or a percentage value.

Example:

A DBMS server with 384GB RAM is running DBMS software in a 3 node cluster. DBMS can run on any one of the 3 nodes.

A single physical server with 384GB of RAM has SAP instances each with a PHYS_MEMSIZE of 32GB plus a Java Instance with a HEAP size of 2GB. The total SAP

memory is at least 224GB. The remaining unused RAM can be used in case another instance needs to be added or if the SAP systems have inefficient custom

ABAP code that consumes a lot of extended memory.


12/16







1. Virtual machine configuration can be up to the total number of vCPU and vRAM or Hyper-Visor limit. Virtual Machines configuration must follow the


2. 10 Gigabit Network with SRIOv is recommended to improve network performance

3. PHYS_MEMSIZE should be set on Virtual Machines in case Dynamic Memory feature is used

4. It is not recommended to use Dynamic Memory in conjunction with automatic DBMS memory management features.


ASCS in 2 node cluster running on two small VMs. The ASCS and ERS consume very little CPU, memory, network and IO.



Notes 1634991 - How to install an ASCS or SCS instance on more than 2 cluster nodes?

1678705 - Installation scenarios for a standalone ASCS instance


13/16


14/16


8 socket servers running in 3 tier configuration can deliver ~1,000,000 SAPS for a single SAP component. SAP customers with more than 20 application servers

have demonstrated near linear scaling with the addition of application servers.


Therefore a 1:4 or 1:5 or greater ratio between DB and application server resources is normal for large systems.Experience from real customer deployments has shown capacity can be scaled very effectively by adding application servers.

The bottleneck is typically not the DBMS server hardware.

10 Gigabit network and a separate dedicated internal SAP application server DBMS network is mandatory for such systems.

Real customer deployments of very large systems with > 15,000,000 dialog steps per day are sometimes constrained by locking/blocking on critical tables such as

NRIV. Application logic and/or business processes must be changed to alleviate such issues. The addition of hardware resources will show little or no benefit


DBMS Server

1. 8 socket Intel server with 512GB to 4TB RAM

2. DBMS software should be configured to use a large data cache to reduce physical disk IO. SAP customers deployed on 1TB 8 socket systems are running

with DBMS cache size of 940GB (nearly all available RAM is allocated to buffer). DBMS software is NUMA aware and can efficiently run across NUMA

nodes.




DBMS cache size set to 1TB there would be very minimal physical disk IO. Analysis of customer systems has shown when the DBMS cache size is more



Physical write will occur as most DBMS use write ahead logging.

6. SSD disk can be used for temporary DB storage spaces and for transaction logs if these physical write operations to disk become critical

7. Some DBMS have fully automatic memory allocation. In such cases the DBMS can be set to auto and use memory as needed (eg. SQL Server). OtherDBMS software will require configuration of fixed amounts of buf fer cache for each system

8. Some DBMS software requires manual configuration to enable NUMA and Large Memory Page Sizes. Consult the DBMS vendor and/or hardwarevendors best practice document for large scale up deployments.


1. Between 6 to 30 physical servers 2 socket Intel E5 32 threads / 16 cores / 2 NUMA nodes / 384GB RAM (192GB RAM per NUMA node)


3. PHYS_MEMSIZE of all SAP ABAP instances and HEAP of all SAP Java instances should be less than the total physical memory of the server.

4. PHYS_MEMSIZE can be set to either a fixed a mount of RAM or a percentage value.


15/16

Example:

A DBMS server with 1TB RAM is running DBMS software in a 3 node cluster. DBMS can run on any one of the 3 nodes.

Physical or virtual servers as required between 6 to 30 balanced with SAP Load Balancing.

Approximately 50 work processes per each ABAP instance. Performance testing has shown many smaller ABAP instances deliver better throughput than a fewlarge instances. If more work processes are needed it is best to install another instance





The amount of RAM and threads required exceeds that currently offered by both VMWare and Microsoft Hyper-V. DBMS software would need to run on

physical servers. 8 socket systems offer 160-240 threads and 4TB RAM which is well in excess of any Hypervisor currently available in September 2012.


1. Virtual machine configuration can be up to the total number of vCPU and vRAM or Hyper-Visor limit. Virtual Machines configuration must follow the


2. 10 Gigabit Network with SRIOv is recommended to improve network performance

3. PHYS_MEMSIZE should be set on Virtual Machines in case Dynamic Memory feature is used

4. It is not recommended to use Dynamic Memory in conjunction with automatic DBMS memory management features.


ASCS in 2 node cluster running on two small VMs. The ASCS and ERS consume very little CPU, memory, network and IO.



Notes 1634991 - How to install an ASCS or SCS instance on more than 2 cluster nodes?1678705 - Installation scenarios for a standalone ASCS instance


16/16

Network Configuration

Review this blog: How to Setup a D edicated SAP Application Server to DB Server Network
http://blogs.msdn.com/b/saponsqlserver/archive/2012/03/31/how-to-setup-a-dedicated-sap-application-server-to-db-server-network.aspxhttp://blogs.msdn.com/b/saponsqlserver/archive/2012/03/31/how-to-setup-a-dedicated-sap-application-server-to-db-server-network.aspx

Documents

HW Deployment DIAGRAMS - Version 6 4