I can't give a link but engineers from oracle often talk about it during public speaking. And this recommendation is not only java specific: if you have a lot of ram (1 TB is gigantic!) then you need big pages instead of the default 4kb so CPU TLB cache would work effectively and OS would be easier to manage ram. In java it's easy to enable by parameters.
I migrated our specific workload to TransparentHugePages (THB) because we use AlwaysPreTouch, so we pay some extra time in the beginning to have less fragmented heap. However, it isn't obvious that you should always go them enabled by default, it can cause perf degradation, check https://www.evanjones.ca/hugepages-are-a-good-idea.html
it's general recomendation to UseTransparentHugePages on heap starting of few GB :)
Oh, didn't know about that as general recommendation. Could you point to the doc?
I can't give a link but engineers from oracle often talk about it during public speaking. And this recommendation is not only java specific: if you have a lot of ram (1 TB is gigantic!) then you need big pages instead of the default 4kb so CPU TLB cache would work effectively and OS would be easier to manage ram. In java it's easy to enable by parameters.
I migrated our specific workload to TransparentHugePages (THB) because we use AlwaysPreTouch, so we pay some extra time in the beginning to have less fragmented heap. However, it isn't obvious that you should always go them enabled by default, it can cause perf degradation, check https://www.evanjones.ca/hugepages-are-a-good-idea.html