Winsat performs work using built in windows components to provide a baseline relative perf estimate. The framework tries to minimize interference with the rest of windows to give you an estimate of hardware capabilities.
Its a log scale that goes to 9.9.
Some of my code is used in that test and yet i never got a clear understanding from that team about who the numbers are for. Customers like to see pretty numbers. Not many people bother to dig into what the numbers mean, and if you do youll find its a bunch of random tasks. Its a generic perf estimate that doesnt match any actual user.
In real life you have a task that you want to run fast - use that task as a perf test.
What exactly are you doing that feels slow?
I am still using a pair of 7 year old machines and am delighted by day to day perf. Big jobs on those machines run overnight where the latest machines would finish in an hour… one of these days ill upgrade…
If ‘windows feels slow’ then it might be antivirus, a virus, or some windows issue with caching.
Biggest cause of degradation in my machines is ssd lifetime. Ssd fail over time and are designed with extra capacity but that capacity is slowly lost to wear. Towards the end the ssd will write very slowly. Try using your ssd vendors disc tools to investigate the state of your ssds?
Ignore winsat its dumb.
