Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: