Earlier quoted context omitted.
Prelim benchmarks show a significant impact (~20%) on Postgresql benchmarks.
20% when running SELECT 1; over a loopback network interface, not in real-world workloads. The other benchmark that has generated some consternation is running 'du' on a nonstop loop. Both of these situations are pathological cases and don't reflect real-world performance. My guess is a 5-10% performance hit on general workloads. Still significant, but nowhere near as bad as some of the numbers that are getting throw…
Your last link is all gaming benchmarks, which as the article mentions are not affected much.