The impact of this could be huge when you look at it from a server perspective. If laptops and PCs slow down by 30% then the general public will grumble about it and eventually get used to it, but servers are usually sized on required performance v load. If suddenly we need 30% extra CPU resource to get the same application performance, that's going to impact hosting costs for *everything*. While CPU is not the only factor in server costs, its a significant one (storage and networking being the others). Say its 1/3rd the cost of a server for simplicity - as of Tuesday afternoon, every application server, web server, email server, streaming server, etc etc could suddenly jump in cost by 10%, assuming we want performance to stay the same (and users always do). Someone has to eat that extra cost, and its not going to be the hosting providers. Ultimately it'll trickle down to the consumer as such things always do.
I have a few CPUs mining cryptonight - the i5 in my workshop PC actually does 210H/s which is better that my GTX960! From what I know of this flaw, I don't think it will actually have much impact on mining as the flaw is based around protected system-level stuff in the CPU kernel. The performance hit comes from having to switch between user and system level processes, as the CPU has to flush it's cache every time. Mining is all compute and so shouldn't actually need much, if any, kernel type activity, but it all depends on whether MS have applied any finesse to the patch or just bashed it with a rock. It shouldn't have any impact on GPU mining.
|