Slow Domain Controller

[miveli]

I have just started with a new company and have been given the task

of fixing a slow performing DC. The server in question has the

following config...

ESX 3i U2

Windows Ent 2003, SP2

4096 GB Memory ( I am going to recommend changing this back to 2048MB )

4 vCPU's ( I am going to recommend changing this back to 1vCPU )

Pagefile = C:\ , 4096MB (recommended 5758MB) ( I am going to recommend changing this to the recommended size for 2048MB )

C:\ = 40GB

D:\ = 25GB

I

am hoping that someone would like to give me their thoughts on the

current setup and whether i am close with my recommendations.

[Dave_Mishchenko]

Your discussion has been moved to the VI: Virtual Machine and Guest OS forum.

Dave Mishchenko

VMware Communities User Moderator

[Lightbulb]

By slow performing what do you mean? DCs tend to not need alot in the way of hardware. Issues with delayed logons are more often caused by improper site design. Also it is possible that if the DC is sharing a subnet that is saturated with some other form of network activity (A master backup server) , overall performance may be degraded (A good indicactor of this are 1054 error in the system log of clients).

[NTurnbull]

Hi, I think that your already on the right track by recomending removing the extra vCPUs. Since this vm has 4 vCPU allocated to it for any cpu calculation ESX will not allow that to run until it has 4 physical cpus that are free. Have a read up on cpu scheduling. You can prove that this is the case from the VC performance monitoring by looking at the cpu wait state counter.

Thanks,

Neil