Disable SSL Encryption to Increase VMware Converter Standalone 5.0 / 5.0.1 Performance


Today I had a maintenance window to clone 7 physical machines twice to create 2 “production mirror” test environments.  Despite a rocky start for other reasons, I kicked off the P2V before heading home.  After checking in after dinner time, I noticed there was no way I’d finish the conversion once before the window ended, let alone twice.  After some searching, I found a reference to disabling  SSL encryption in VMware Converter Standalone 5.0, documented in KB2020517.

I had 7 simultaneous transfers from 1 gigabit connected physical machines.  My converter workstation is connected at 1 gigabit as well, and the host had no other VM’s running and had 4 1 gigabit network connections, but the transfer rate was only 500 KB/s to about 2.5 MB/s, according to converter.  After disabling SSL, I cancelled my jobs and each one went up to 10 MB/s or more, bringing my combined total up to around 90 MB/s.

The VMware article is below.

Disabling SSL encryption on VMware Converter Standalone 5.0

Purpose

By default, the VMware vCenter Converter Standalone 5.0 default the converter worker encrypts the data stream using SSL. Encrypting the traffic increases security, but it can decrease performance.
This article provides steps to disable SSL encryption in VMware vCenter Converter Standalone 5.0.

Resolution


To disable SSL encryption for the converter worker:

  1. Locate the converter-worker.xmlfile. By default, it is located at:
  • Windows 7 and 2008 Server – C:ProgramDataVMwareVMware vCenter Converter Standalone
  • Windows Vista, XP and 2003 Server – %ALLUSERSPROFILE%VMwareVMware vCenter Converter Standalone
  • In older Windows versions – %ALLUSERSPROFILE%Application DataVMwareVMware vCenter Converter Standalone
  • Take a backup of theconverter-worker.xmlfile.
  • Open the file in a text editor and locate the tag pair. It is located inside thetag and has a value oftrue.
  • Change the value tofalse.
  • Save and close the file.
  • Restart the VMware vCenter Converter Standalone Worker service on the machine.
  • Leave a Reply