New! Listen to this post in our daily podcast.
by
Brian Madden
Now that Gabe and I are back from the holidays, we’re getting ready to spend some quality time with several of the recently-released VDI products (both for our “VDI Week” and for our general knowledge and articles.) One of the first things I want to test is VMware’s software implementation of PC-over-IP that’s built-in to View 4. Most remoting protocols work great over the LAN—the real test comes when you start adding congestion and WAN-like characteristics.
Last month I asked (via twitter) about which free network simulation and WAN emulation tools people use. People shared a ton of ideas (WanEm, WANulator, and GNS3 seem to be the most popular), and these things are all pretty simple to use.
So now that I’m sitting here with my View 4 lab and my WAN simulator in place, I’m all ready to go. The only problem is that I don’t have a clue as to what values I should configure the WAN simulator for? Sure I could pick some arbitrary numbers, but I’m more curious about what real-world numbers would be most valuable to you?
In other words, what WAN parameters should I use that will prevent comments like, “Your test is *** because you didn’t test x scenario?”
By the way, if there’s one thing I’ve learned over the past twelve years working with ICA, it’s that everyone has his or her own threshold for what makes a “good” user experience. So rather than me trying to see that a particular protocol works or does not work over a particular set of WAN parameters, it will be much more valuable to record videos of the actual client screen output.
I’m not trying to be super-scientific about this since I’m not a real analyst and I don’t care about it that much... I just want to know maybe three or four test scenarios I should use as I’m trying these products out?
(Note: You must be logged in to post a comment.)
If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.