Explore >> Select a destination
|
You are here 
|
www.evanjones.ca | ||
| | | | |
mazzo.li
|
|
| | | | | Let's say that you have a program which relies on huge pages for performance. I couldn't find a resource fully explaining how to allocate huge pages at runtime, making sure that the huge page allocation was successful, so here it is. | |
| | | | |
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. | |
| | | | |
danlark.org
|
|
| | | | | TCMalloc team recently published a paper on OSDI'21 about Google's allocator internals, specifically on how huge pages are used. You can read the full paper here. TL;DR. Google saved 2.4% of the memory fleet and increased the QPS performance of the most critical applications by 7.7%, an impressive result worth noting. Code is open sourced,... | |
| | | | |
justinpombrio.net
|
|
| | | |||
