Recommendation
To test the MTU size of 9,000, the database was running an OLTP workload while the virtual machine was moved using vMotion to another server. We captured the time to vMotion the server as well as New Orders per Minute (NOPM) and Transactions per Minute (TPM) for analysis. Increasing the MTU size showed significant gains for these metrics:
A larger MTU size of 9,000 reduced the time to complete moving the database with an active workload compared to the default MTU size of 1,500. This impressive time-saving function led us to label this best practice as a Day 1, Highly Recommended procedure.
NOPM and TPM also increased, but not as substantially as the vMotion time savings. The overall benefit of this best practice is that database performance has greater consistency during vMotion with a substantial time-savings in moving the database.
Implementation Steps
Process to configure MTU size = 9000 for vMotion network
Note: To change it at network switch level, login into switch console and update the MTU