SAP HANA Over VMware - compute resource sizing

[micahwillliams]

This weblog does no longer describe a way to perform the actual SAP HANA system RAM sizing. For this please refer to the SAP documentation. an awesome begin is to study the sizing SAP HANA Sizing approaches presentation, which describes the SAP HANA QuickSizer and ABAP SAP HANA sizing reviews to be had for sizing SAP HANA structures. also an excellent start is the Sizing tactics for SAP HANA file.

CPU and RAM Sizing SAP HANA on VMware vSphere

Sizing SAP HANA isn't the same as sizing a classical SAP application. rather that specialize in CPU assets, for SAP HANA memory is the focal point and what number of CPU assets are required to support a selected amount of RAM. Beside this, we need to consider the exceptional CPU and RAM maximums of vSphere five.five and six, because it defines the maximal length of a digital SAP HANA VM. To make it even greater complicated, we have to consider which workload (SoH or BWoH) will run on the chosen SAP HANA gadget, which CPU and which HANA SPS version gets used, as one-of-a-kind CPU socket to RAM ratios exist for all of this mixtures.

That is a theoretical sizing maximal parent and were given calculated with the referenced sizing components as documented inside the “structure hints and first-class Practices for Deployments of SAP HANA on VMware vSphere” file, a good way to to be had on www.vmware/pass/sap-hana.

The RAM sizing predicament should get seen as the first begin to length the VM and the RAM may additionally get extended and aligned to the actual server usage and CPU usage. If in production the server by no means reaches its CPU limits then it's miles feasible and supported to increase the vRAM of the VM.

Sizing instance:

Assumption: VMs for 2 SAP ERP and one present BW machine needs to get sized. The SAP sizing reports provide following RAM sizes together with facts increase as defined inside the file the subsequent years.

ERP SID1 – 444 GIB

ERP SID2 – 165.2 GIB

BI – SID3 – 1009 GIB

The overall RAM wanted might around 1620 GIB + the RAM wanted for vSphere (+1.5% = total 1644 GIB). considering SoH and BWoH ought to get consolidated at the identical server, the chosen server has to be certified or supported to run BWoH. The RAM requirements (512 GB consistent with socket max.) of this SAP HANA BW software kind may be the leading issue for this configuration.

SAP HANA CPU socket to RAM Ratio

The CPU socket to RAM ratio relies upon at the used CPU generation, the HANA SPS degree and the SAP HANA workload kind so that it will get deployed.

Finding out the CPU socket to RAM Ratio is relatively easy as it simply dividing the maximal RAM supported in a SAP HANA certified server for BWoH or SoH and a particular SPS stage.

With above CPU Socket to RAM ratios we will now calculate how many sockets a server wishes to have and how many NUMA nodes / CPU sockets a VM will must get assigned with.

Which server wishes to get purchased?

Total wished RAM consisting of vSphere RAM want divided through the BWoH CPU Socket to RAM ratio, as one of the HANA VMs can be a BW HANA VM. –> 1644 GB RAM / 512 GB RAM = three.21.

This means a four socket BWoH HANA server with a complete of 2 TB RAM set up could be enough to guide the planned HANA VMs. interest, the 512 GB RAM per socket are best to be had with a Haswell server and SPS11. If SPS11 can not get used, then a one of a kind Socket to RAM ratio will want to get implemented.

Pick out now an authorized server configuration listed on the licensed SAP HANA hardware listing can get selected. We also recognize now; that vSphere 5.five might be sufficient to support this configuration.

How does the SAP HANA VM configuration look like?

Identical calculation as before, we divide the sized SAP HANA RAM by using the RAM mounted in a CPU socket. ->

ERP SID1 – 444 GIB / 512 GB RAM = 0.87 x RAM of CPU socket

ERP SID2 – one hundred sixty five.2 GIB / 512 GB RAM = 032 x RAM of CPU socket

BI – SID3 – 1009 GIB / 512 GB RAM = 1.97 x RAM of CPU socket

due to the fact we've production stage SAP HANA VMs, we need to spherical-up the calculated CPU sockets and will assign all to be had CPU and RAM resources to the VMs which might be available within the assigned sockets, minus the RAM needed for vSphere.

ERP SID1 – VM = 500 GB RAM and 36 vCPUs

ERP SID2 – VM = 500 GB RAM and 36 vCPUs

BI – SID3 – VM = 1024 GB RAM and 64 vCPUs (CPU restrict)

below determine suggests the VMs strolling on a single SAP HANA supported four socket, 144 thread, 2 TB RAM HANA server. while deployed as equipment systems, then three physical server structures must get deployed rather than handiest personal server device as proven, while the patron does now not want to leverage the multi-tenancy SAP HANA characteristic.

When configured for non-prod VMs then the calculated, smaller, VM configuration as decided on for the manufacturing environment would be possible. here is to say that the smallest vCPU be counted of a SAP HANA VM is 10.

Example for non-production SAP HANA VM whilst using the formulation posted inside the the structure manual. For info please consult with this record as soon as available.

ERP SID1 – VM – 18 vCPUs and 444 GIB vRAM

ERP SID2 – VM – 10 vCPUs and one hundred sixty five GIB vRAM

BI – SID3 – VM – 42 vCPUs and 1009 GIB vRAM

unfastened sources: seventy four CPU threads and 430 GB RAM for other VM(s)

Sizing the non-prod VMs with the calculated figures, would allow to apply the non-applied seventy four CPU threads and 430 GB RAM (-1.5% = 420 GB) for different workloads, like to different SAP HANA VMs or to reserve those loose resources to provide VMware HA sources for potentially failing VMs of other host systems that now may additionally get restarted in this host. beneath instance indicates how use a number of the free sources with the aid of sharing NUMA node 3 and 4 with other non-prod HANA VMs.

Conclusion

The examples display a vSphere 5.5 based totally server configuration, however the statistics published above also are legitimate for calculating vSphere 6 primarily based VMs. The most effective difference is that the CPU quandary is not 64, however 128 vCPUs and instead of 1 TB vRAM, it'd be four TB vRAM. it is also critical to word that not handiest the vSphere VM sizes are defining configuration barriers, but additionally the SAP HANA supported hardware configurations and SAP HANA SPS tiers! Over the time SAP may additionally alternate the CPU to RAM ratios to the fantastic or, if new evolved SAP HANA local packages require extra CPU sources, to the negative, as extra CPU strength maybe required to system the configured RAM of those possible new programs.

[parmarr]

Thank you for the content and information. We truely appreciate it!!