|
@AndresFreundTec | |||||
|
The magic necessary (linker flags to align the text sufficiently, link to libhugetlbfs, editing elf headers with hugeedit --text, setting up accessible hugetlbfs) seems too big for most, but I wonder if there's a way that could be simplified.
|
||||||
|
||||||
|
Andres Freund (Tech)
@AndresFreundTec
|
6. sij |
|
Interesting.
Doing the necessary rituals of sacrifice to get postgres started with the text segment mapped as huge pages yields nearly 10% speedup in a highly concurrent workload.
|
||
|
|
||
|
Andres Freund (Tech)
@AndresFreundTec
|
6. sij |
|
7.608 M/sec iTLB-loads w/ 50.80% iTLB-load-misses for normal mapping, vs 1.547 M/sec iTLB-loads w/ 48.82% iTLB-load-misses with text mapped as a huge page.
|
||
|
|
||
|
Andres Freund (Tech)
@AndresFreundTec
|
6. sij |
|
Oh, and besides being complicated: It currently also breaks perf profiles...
|
||
|
|
||