News for hackers. Stuff that matters.
Re:Google Chrome’s new Meltdown and Spectre safeguard is a m... by herne on Saturday July 14, 2018 @11:56AM (#17530811)
The article didn't link to the actual blog post: https://security.googleblog.com/2018/07/mitigating-spectre-w... which has some more nuance:

"on the plus side, each renderer process is smaller, shorter-lived, and has less contention internally, but there is about a 10-13% total memory overhead in real workloads due to the larger number of processes"

Re:Google Chrome’s new Meltdown and Spectre safeguard is a m... by bilbo0s on Saturday July 14, 2018 @12:52PM (#17531081)
That doesn't even really tell us much.

We need more information. For instance, it would be enlightening to have an understanding of how, exactly, a "real workload" is defined? How many tabs? What's going on in the tabs? Etc. A definition of "real workload" would at least allow us to compare that workload to our own typical workloads. (Which I assume would likely be different for an administrative assistant vs an executive vs a developer vs a researcher vs etc etc etc.)