|
You are here |
www.evanjones.ca | ||
| | | | |
rigtorp.se
|
|
| | | | | In this article I will explain when and how to use huge pages. | |
| | | | |
prodfiler.com
|
|
| | | | | ||
| | | | |
blog.nelhage.com
|
|
| | | | | tl;dr "Transparent Hugepages" is a Linux kernel feature intended to improve performance by making more efficient use of your processor's memory-mapping hardware. It is enabled ("enabled=always") by default in most Linux distributions. Transparent Hugepages gives some applications a small performance improvement (~ 10% at best, 0-3% more typically), but can cause significant performance problems, or even apparent memory leaks at worst. To avoid these problems, you should set enabled=madvise on your server... | |
| | | | |
kstefanj.github.io
|
|
| | | I've recently spent a lot of time in memory reservation code of the JVM. It started out because we got an external contribution to enable use of multiple large page sizes for Linux. To do this in a good way some other things had to be refactored first. While taking this trip down memory lane I realized that doing a short summary of how large pages are used by the JVM might be an interesting read. | ||