• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

vSphere client rant

T

Thuleman

Supreme [H]ardness
Joined
Apr 13, 2004
Messages
5,833
Alright, I just need to vent a little, if you are not in the mood for highly opinionated content, skip this post. ;)

I am growing quite tired of the vSphere client.
The input lag when using the console is simply unacceptable. With VMware tools installed on Windows Server 2008, 3 hops on a 100Mbit connection, <10ms latency, there is what I would consider to be substantial input lag when running the VM at 1280x800.

Same VM via 5 hops, 1Mbit connection, <40ms, input lag is such that the mouse is essentially unusable.

13 hops, ~700ms (don't ask!), forget about it, console unusable.

I didn't use the 13 hop connection with 3.5, but I did use the exact same connection for the 3 and 5 hop cases under 3.5 and it worked just fine. Tbh, the console is worthless to me on the 5 hop connection. That's just not right.

Moving on to FIXED WIDTH vClient?!? WTF! Seriously, fixed with at roughly 925 px is total bullshit. Dealing with horizontal scrollbars just because someone didn't have enough foresight to set the fluid width flag is imho unacceptable.

There you have it, thanks for reading, I do actually feel a little better now.

Disclaimer: I am stuck for 2 weeks on the 13 hop ~700ms latency connection, and that does make me a bit grumpy. Between the latency and literally being at the end of the Earth I am not much of a happy camper right now.
 
Do you have a 2003 VM to compare with? My experience with 2008 is that even with VMware tools installed, there still is significant lag when local to the ESX host (1 hop, 5ms lag at max). This lag does not exist with 2003, in my testing.
 
Host OS is Vista 64.

I monkeyed around with this a little more and I found that there's very little lag, nothing unexpected considering the shitty connection I am on, when using RDP. vSphere client console remains unusable under the same connection conditions.

I can try a 2003 install over the weekend and see whether there's any difference. Will report back.
 
Yeah, try 03 and XP. I have a feeling it's a vista issue, which I deal with too, and my machine is right next to my host :p
 
Someone on the vmware forums suggested to install the client on a VM, and then just RDP to that box, then console in to the other machines. This may seem crazy, but actually works remarkably well. My RDP is responsive even on the 700ms connection, and the console is responsive enough to actually do stuff on other machines.
 
Yeah - I really think it's XP. Technically, the client just became supported there... :(
 
Trying not to de-rail this thread but it is similar. Has anyone using the new vsphere client noticed that when switching to the console it takes a good 15-30 seconds for the console to show up?

Using the vsphere client on Windows XP with the same test machines that I was using for 3.5 update 3 and never had this problem until the upgrade. Luckily it is just a test environment.
 
You must log in or register to reply here.
Back
Top