The overall architecture of SAP HANA on Azure (Large Instances) provides an SAP TDI certified hardware configuration (non-virtualized, bare metal, high-performance.

Note: Your browser does not support JavaScript or it is turned off. Press the button to proceed. Smith Micro Poser Pro 2014 Sr3 Torrent here. Cisco UCS Configuration Principles for SAP HANA with Shared Storage and Shared Network. Global Hardware Requirements for SAP.

This is the second blog of my SAP HANA on vSphere blog series and will provide information on SAP HANA on VMware vSphere compute resource sizing. This blog got updated on November 23rd 2016 to include the Intel Xeon Ex-v4 CPUs (Broadwell), which are now supported. Sizing SAP HANA database starts with the determination of the database size. Download Devon Ke Dev Mahadev Song Karpur Gauram. This can get done either by using the application (new system), or by running a specific SAP HANA sizing report (existing systems), as documented in SAP note (S4/HANA) and SAP note (BW). Beside determining the database size of HANA that will get operated in RAM, it is also necessary to size the needed resources for the application server stack.

This can get done by using he SAP HANA Quick Sizer as this tool will provide the necessary system configuration required for the application part of a SAP HANA based business application. This blog does not describe how to perform the actual SAP HANA system RAM sizing, for this use above tools and methodes. For details read the sizing presentation, which describes the SAP HANA QuickSizer and ABAP SAP HANA sizing reports available for sizing SAP HANA systems. Also a good start is the document. (Attention you may require a SAP SDN account to access the SAP HANA sizing documents). CPU and RAM Sizing SAP HANA on VMware vSphere Sizing SAP HANA is different from sizing a classical SAP application. Instead focusing on CPU resources, for SAP HANA memory is the focus and how many CPU resources are required to support a specific amount of RAM.

Beside this, we have to consider the different CPU and RAM maximums of vSphere 5.5 and 6, as it defines the maximal size of a virtual SAP HANA VM. To make it even more complex, we have to take into account which workload (SoH or BWoH) will run on the selected SAP HANA system, which CPU and which HANA SPS version will get used, as different CPU socket to RAM ratios exist for all of these combinations. In the soon to get published new “ Architecture Guidelines and Best Practices for Deployments of SAP ® HANA ® on VMware vSphere ®” document, which will be available on, I have detailed sizing formulas specified, which I have defined jointly with SAP.

The formula respects hyperthreading with a performance gain of 15% and the used CPU type (amount of available cores), virtualization memory costs and can get used also to calculate the needed vCPUs to support a certain amount of HANA RAM. Instead of using these sizing formulas, I will explain a simplified way how to size production level ready SAP HANA VMs that respect the SAP defined CPU socket / RAM ratios. Since we want to leverage hyperthreading, it is required to enable it on the host and that the VMs get configured with the parameter Numa.PreferHT=1. Using this parameter ensures NUMA node locality and forces the ESXi scheduler to use hyperthreads instead of potentially idle cores on other NUMA nodes. Colorspan Sevice Manual on this page. More detailed explanations will be available in the referred VMware SAP HANA guide. As well as storage and network sizing and configuration information. VMware vSphere SAP HANA relevant Sizing figures Before we start to size SAP HANA VMs, we have to discuss the current vSphere compute resource maximal sizes and define the current sizing limitation for memory.

This limitation is important to understand when sizing a BWoH system on vSphere, as the CPU VM limitation of vSphere 6 of 128 vCPUs will not allow to utilize the theoretical maximum of 4080 GB per VM. Reason is that SAP has defined specific CPU socket to RAM ratios, which are more demanding for an analytical workload like BW.

For OLTP like applications like SoH this ratio is higher and here we could size larger memory sizes as even vSphere supports (see below table)! The table enumerates the current maximal sizing figures for virtualized SAP HANA systems on vSphere. Please note that these figures represent the theoretical sizing maximal sizes and should get aligned after some time to the real live SAP HANA configuration, as you may have less CPU resource need and would therefore be able to increase the memory beyond this theoretical sizing figures.

If more VMs get installed on a server or when a single VM will consume the complete available RAM, then also RAM for vSphere has to get reserved. We calculate 1 percent up to 3 percent for vSphere. This depends on the actual VM configuration. ↓ • Hi Erik, thanks for sharing these ratios and sizing examples. It is hard to find offical statements because the new documentation (Haswell+vsphere 6 / “Architecture Guidelines and Best Practices for Deployments of SAP HANA on VMware vSphere”) is still not released. In your example you use 2xERP (SoH) and one BW/BI (BWoH) system.