VMware View 3.1 Admin Console Slow

[rtackett]

Why is the VMware View 3.1 admin console so slow? Are there any tuning techniques?

[AndreTheGiant]

Do you mean View Manager Console?

Please, give some infos on View Manager Manager server (CPU, Mem).

Andre

[rtackett]

My configuration is as follows:

View 3.1

Virtual Center 2.5 U4

VMware ESX 3.5 U4

View Server Hardware:

HP Proliant DL380 G5

Dual CPU - Quad Core

4GB RAM

(2) 72GB SAS drives

1GB NIC

Approximately 400 users.

[AndreTheGiant]

400 users are a big number for a single server.

Have you check with performance monitor to see if you have memory issues?

Andre

[rtackett]

Well, according to the specs I've gotten from our VMware SE, that is an acceptable number for single server. I'm also using direct connect for the clients instead of tunneling via SSL.

Technically I have three servers with two of them being dual CPU VMs with 2GB of RAM. They are in our production server environment and not in the VDI environment.

I've gone throught he performance stats and we are not hitting any of the hardware very hard. Out of 4GB of RAM we are using around 1GB total and the CPUs idle around 10% with spikes up to about 70% when logging in to the site. The users don't experience any of this when using the full client, the web client or they Wyse thin clients running WTOS. It's only the admin console that's extremely slow.

[AndreTheGiant]

The console in slow in each tasks?

Maybe there are some other bottleneck.

The VC is working fine?

Andre

[rtackett]

The console is slow for all tasks, including logging in. The log in process takes approximately 30-45 seconds.

We do have a very large directory with a base root domain and several forests.....could domain enumeration be the cause of the slowness? The VC server and database are pretty bulky servers as well and don't seem to be suffering.

[AndreTheGiant]

could domain enumeration be the cause of the slowness?

Maybe.

The DC that you have configured in View Manager is a GC?

Andre

[rtackett]

I guess I don't understand what you mean. I don't see a setting anywhere in the View admin console to configure which domain controller or how you communicate with the domain.

[AndreTheGiant]

Right, it is done by ADAM.

Maybe there could be some optimization at this level, but I do not know.

Andre

[rtackett]

OK. So, assuming that this is where the problem lies, that makes sense.

However, is that really the problem?

[admin]

At that pool size it sounds like the bottleneck could be with your DC. usually ours don't start to get noticably slower until we hit around 2000. In the situations in which we are running/testing view the DC is the DNS server so that controls which DC we are using.

Have you tried restarting the VMware view connection server service on the connection server? Sometimes that helps when the view is misbehaving, if you are running in direct connect mode this shouldn't interupt any clent to agent sessions.

-Ivan Weiss

Please award points for "correct" or "helpful" answers if you find the information I have provided to be useful.

[jkatz71]

I know what you mean. The admin console has always been slow. It got better in the 3.1.1 release but it's still pretty slow going from tab to tab. We're also running in direct connect mode so there shouldn't be any consistent load on the View server. It was quicker when we were testing it with a dozen user vms, but now that there are closer to 2 hundred it is much slower. And FWIW, memory/CPU don't seem to be getting maxed out either.

-jonathan