1 of 1 people found this helpful
At a driver level, we do a pretty good job of monitoring perfomance of key functions to make sure that performance maintains or improve from release to release. That is why we have a Validation team and release criteria that we set for every release that include performance.
What we can't do is look at every performance tool, or understand the ramifications of all changes made to the driver. We do not use PassMark as part of our validation suite so we have not monitored whatever combination of functions it uses to evaluate performance.
Because we have not measured any significant decrease in performance in the driver version to version, my guess is that we have affected a system change that has impacted whatever narrow window of functionality that PassMark monitors. Likely what has happened is that we have added additional 3D capability to the driver between V8 and V10 and Windows is now attempting to use that new 3D capability in the driver for its 2D functions. That is not under our direct control, and is not always a smart thing to do. As graphics operations become more complex, the use of an accelerator is usually a good thing to speed it up. THere is a crossover however where the overhead of transfering a function from the CPU to the GPU and back is greater than the time savings of using the GPU. This is normally the case with 2D (and things like Windows Presentation Foundation 2D functions) where using the 3D acceleration slows down the 2D operations yet Microsoft seems to insist on using them and using them very inefficiently. You might be able to verify this by going into your system performance settings and setting back the overall hardware acceleration usage a notch or two and see how that impacts PassMark performance on IEGD 10.4. My guess is that it will improve thus showing what MIcrosoft is trying to do under the covers.
Hope this helps, Kirk