60 FPS, a chopper crashes into a building in front of you which then partially collapses, it dips to 30 FPS and gameplay gets slow
90 FPS, a chopper crashes into a building in front of you which then partially collapses, it dips to 60 FPS and gameplay stays the same
You don't understand how VirtuMVP works then. The only performance gains achieved were under situations where you don't see spikes, and with it enabled the spikes were more severe. It doesn't raise the ceiling for your FPS, it just makes it look like your rig is performing better than it actually is. Essentially, it does absolutely nothing other than allow a few idiots to gloat about how big their e-penis is.
Secondly, unless you're running a multi-monitor setup or playing a very very CPU intensive game that's poorly programmed (like ARMA 2 or Red Orchestra) or highly CPU demanding (BF3 in multiplayer), you won't see a difference in gameplay between an older CPU and a $1000 3960X. Most games are console ports, thus the hardware really doesn't make as big of a difference as it once used to, particularly on the CPU side as game developers have been leaning far more heavily on the GPU.
In terms of how Virtu functions, it is important to understand the concept of being able to perform what was mentioned on the previous page—being able to manipulate what the GPU does and what it does not do. The underlying technology of Virtu is that the environment is virtualized. This means that instead of the GPUs working on top of the operating system, Virtu adds in a middle layer between the operating system and the GPU. This way, Virtu can manipulate everything that the operating system wants to say to the GPU, and vice versa, without either of them knowing that there is a middleware layer.
The second is most important perhaps, which I will go into later. Virtual V-Sync and HyperFormance will only make a difference in the following circumstances:
a) You suffer from visual tearing in your games, or you actively use V-Sync
b) If your setup (screen resolution and graphics settings) perform better than your refresh rate of your monitor (essentially 60 FPS for most people). If you have less than this, then you will probably not see any benefit.
As for a), nVidia has already has a better solution with their adaptive V-sync on the new Kepler series cards, and
b) basically states that when you want it to perform better it won't because it's not meant to. In short, it really does next to nothing. This isn't surprising given that nobody has spoken a word of it since it was initially tested and that was in the pre-release stages when the motherboards weren't available to the public.