3 ms·
They still saw the same performance though due to “true sharing” or CPU enforced memory ordering on a highly contended variable. Patching the JDK to skip the s
by almost_usual 4y ago
They still saw the same performance though due to “true sharing” or CPU enforced memory ordering on a highly contended variable.
Patching the JDK to skip the secondary cache altogether was the real solution.