|
You are here |
kstefanj.github.io | ||
| | | | |
rigtorp.se
|
|
| | | | | In this article I will explain when and how to use huge pages. | |
| | | | |
www.evanjones.ca
|
|
| | | | | [AI summary] The post explains how using huge pages in virtual memory can improve CPU performance by reducing translation lookaside buffer (TLB) misses, while discussing potential downsides like memory fragmentation and compatibility issues with certain software patterns. | |
| | | | |
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... | |
| | | | |
eli.thegreenplace.net
|
|
| | | |||