Advertisement
ii)
Application and file opening time. How long does it take to open an office document?
iii)
File save time. How long does it take to save your document?
iv)
Internet page load time – measuring this can be difficult since it is generally more a
function of the network performance, not the PC itself
v)
Video playback performance. For example, does educational content play smoothly
with synchronized sound?
vi)
System power consumption. How much power is consumed by the system on
average?
However, even in measuring these parameters, the goal is to deliver "responsive" performance,
versus comparing absolute numbers. Will users really notice the difference between 31 second
and 33 second boot times, or 1 second and 1.2 second file save times?
While the host system runs through its simulated work load, we can observe the system resource
utilization through the performance monitor. Ideally, CPU performance should average below
90%, memory utilization should generally be less than the physical amount of memory installed
(no system page thrashing), and the network should be sized and configured properly for the
number of users. If these parameters are maintained, an NComputing environment will give each
user performance that is very close to that of the native host system. (Again, even if the CPU
load goes over 100% the user performance is in most cases is still very good.)
Thus, traditional PC benchmarks are generally not a good measure of real-world user experience
and have been used by the PC industry to promote system capabilities not actually required for
normal user computing. Furthermore, such benchmarks may not even work in a multi-user
environment. However, if you run the simulated workload metrics outlined above you can
demonstrate to yourself that NComputing vSpace virtual desktops deliver a user experience that
is close to that of the host PC.
NComputing is a registered trademark. Other trademarks and trade names are the property of their respective owners. Copyright 2010.
Advertisement
