Skip to Content

SAP on VMWARE How do you manage? Any High Latency Setting Experience?

We are running SAP ECC 6.0 on Windows SQL Server 2016 VMWare VSPhere 6.7.0. Back when we went virtualized in 2014, we had pretty bad performance issues which led us to the white paper Best Practices for Performance Tuning of Latency-Sensitive Workloads in vSphere. There we found settings for improved performance for latency sensitive applications including Interrupt Coalescing, LRO & power management. These settings stabilized our performance.

Fast forward a few years and after OS/DB upgrades we are being challenged by our network team with the specific setting for High Latency which we have enabled. In our environment we do not share resources or vMotion our SAP systems.

So that brings us to our question of how do others run SAP in a virtual environment? Do you share SAP resources? Do you have VMotion enabled? Have you enabled any high latency settings or other Latency sensitive settings?

Our networking teams reasoning behind removing the setting is to enable our hosts to use vMotion and other machines to share resources if they need it. Although I can’t find any supporting documentation that says we can’t vMotion with this setting enabled. Actually note 2015392 states:
Attention! The Latency Sensitivity setting will lead to longer VM boot times due to the memory pre-allocation and longer switch over times during vMotion. This increased vMotion switch over time may lead to a communication interruption between the application server and the database.

There is also the suggestion that if we remove the high latency setting it can be compensated by increasing the CPU cores and processor speeds.

We are hesitant about this change and would love feedback from the community regarding your experiences with Virtualization.

Regards,

Diane Szmurlo

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers