After using PerformanceTest to benchmark my new laptop, I noticed the 2D mark was far below average. I messed around with the resolution and scaling options in windows, and fixed it; my 2D benchmark went from 380 to 600, raising my overall Passmark score dramatically. It turns out, Window 10's scaling dramatically effects the 2D benchmark. The resolution also effects the 2D score as well. I spent the last 2 hours running tests of different scaling percentages and resolutions, and attached is a screenshot of the spreadsheet of my results.
So how is this an error? Well, at 1080p, Windows by default sets the scaling to 125%. If you're on 4k (like me), the scaling default is set at 250%. I expect for this to impact the performance of my graphics card, but PerformanceTest should take this into account, or the 2D benchmarks are going to be vastly inaccurate of the real performance of the graphics card. Just as the 3D benchmark takes into account resolution (and prevents Window's scaling by running everything full-screen at a set resolution), the 2D score should also take the resolution and scaling into account. I did test the 3D benchmark, and the DirectCompute test (only test not run in full screen) is also affected by Window's scaling and resolution.
So how is this an error? Well, at 1080p, Windows by default sets the scaling to 125%. If you're on 4k (like me), the scaling default is set at 250%. I expect for this to impact the performance of my graphics card, but PerformanceTest should take this into account, or the 2D benchmarks are going to be vastly inaccurate of the real performance of the graphics card. Just as the 3D benchmark takes into account resolution (and prevents Window's scaling by running everything full-screen at a set resolution), the 2D score should also take the resolution and scaling into account. I did test the 3D benchmark, and the DirectCompute test (only test not run in full screen) is also affected by Window's scaling and resolution.
Comment