Perfomance issue with OpenLdap in VM

[Stéphane]

Hello,

I have a OpenLdap directory in a VM host by an ESX Server (Bi-Xeon 3 Ghz / 4 G RAM). When I import the database (~3000 accounts) it takes about 35 minutes. When I do the same operation on a physical server (BI-Xeon QuadCore / G RAM) it takes less than 3 minutes. I don't think the difference of the hardware explain all the differences. So, do you have any ideas of way to optimise my VM with OpenLdap ?

Kind regards

[Texiwill]

Hello,

Thread moved to the performance forum....

I run an OpenLDAP server in a VM as well however I do not have any issues with it... Granted I also do not have 3000 accounts. Can you let us know the Guest OS Model and Version as well as the version of OpenLDAP in use.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354, As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[Stéphane]

Hello,

Guest OS is RedHat Enterprise 4 Update 2 (kernel 2.6.9-42) with OpenLdap 2.2.13.

Kind regards

[drummonds]

Stephane,

Usually order of magnitude differences are caused by improper (or incomplete) installation of VMware Tools. Have you installed them and verified that the vmxnet driver is running?

Also, some minor improvements are possible by verifying that you've got the right amount of memory installed, no unneeded vCPUs, optimally configured storage and the like. But those types of changes will usually only result in incremental improvements (10, 20, maybe 30%). As I said, order of magnitude improvements are possible through the addition of VMware Tools.

Scott

[Stéphane]

Scott,

I update my ESX to 3.0.2 to respect pre requires hardware. I upgrade bios of server and vmtools too... The problem still exist... Another idea ?

Stéphane

[drummonds]

Stephane,

First, how have you verified that the vmxnet driver is installed and running?

Next, have you tried following any of the analysis techniques on the page?

Scott