Ha, Intel were *so proud* of their high throughput RDRAND, and now it turns out they leak the values all over the other cores and the microcode patch to fix it... has a 97% performance hit. As in you get ~1/30th of the performance you used to. Whoops! https://www.phoronix.com/scan.php?page=news_item&px=RdRand-3-Percent …
-
Show this thread
-
Hector Martin Retweeted
As @sebsued points out, it may well become a DoS vector itself, because if I understand the mitigation right, RDRAND ops are now *serialized against the entire chip memory bus*. They block all other cores from doing any reads and writes that miss cache. https://twitter.com/sebsued/status/1270639456312311809?s=19 …
Hector Martin added,
This Tweet is unavailable.3 replies 17 retweets 80 likesShow this thread -
I just did a test. One thread of RDRAND on an unpatched Xeon E-2144G (8 threads) drops 7-threaded sysbench performance by 10%. The same with the patch, 55%. So with the patch, a rogue core can now halve your memory performance. But it gets better.
2 replies 33 retweets 115 likesShow this thread -
Running 8 threads (on an 8-thread E-2144G) of RDRAND in the background, memory throughput drops by *81%* with the patch vs unpatched (91% vs idle). So if someone can spawn a bunch of RDRAND threads, they can drop your memory perf to 19% of what it would be, 9% of nominal.
6 replies 42 retweets 132 likesShow this thread -
Replying to @marcan42
I didn't find the time to run this test for the paper, so thank you so much for actually doing it! It was clear it'd be bad given that they put the effort in to add an MSR to disable the mitigations again. It's about the level of performance hit I expected, but.. ouch. Very ouch.
1 reply 0 retweets 7 likes -
Replying to @noopwafel
It was just a quick sysbench thing, not even sure exactly what kind of memory workload it's using, vs "a: rdrand %rax; jmp a", but yeah.... it looks pretty bad.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @noopwafel
might be interesting to see what happens if one wouldn't loop around a single rdrand but a block of 16 or more and see if it makes it even worse.
1 reply 0 retweets 0 likes
I tried that but it didn't seem to be much worse. I think the overhead of the jump is negligible.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.