/explore
|
You are here 
|
rigtorp.se | ||
| | | | |
www.lukas-barth.net
|
|
| | | | | If you build an application that uses large, contiguous amounts of memory, it can increase your performance if you allocate this memory in so-called huge pages. Linux offers you two ways of doing that - a legacy way and a modern way. This article describes the modern way of using huge pages, so called transparent huge pages (THP) and applies the techniques from a previous article to verify that we actually got huge pages. The article starts by giving a super-short recap on how paging works and why huge p... | |
| | | | |
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... | |
| | | | |
rigtorp.se
|
|
| | | This is a short guide describing the latency implications of the virtual memory abstraction. | ||
