- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -

HugePages: Difference between revisions

From HLRS Platforms
Jump to navigationJump to search
No edit summary
Line 8: Line 8:


=== Self compiled applications ===
=== Self compiled applications ===
During Compilation one of the craype-hugepages<size> (i.e. craype-hugepages16M) modules has to be loaded.
* During Compilation  
**one of the craype-hugepages<size> (i.e. craype-hugepages16M) modules has to be loaded.
**This will link the hugepages library to your application.
* During runtime
** Load the craype-hugepages module with the pagesize you want to use.
** The size chosen during runtime is completely independent from the size you have chosen during compilation.
** Therefore you can compile once and test different sizes during runtime without changing the binary.
   
   



Revision as of 15:39, 9 December 2015

What are HugePages?

For an introduction for HugePages check [[ https://en.wikipedia.org/wiki/Page_%28computer_memory%29#Huge_pages |HugePage@Wiki ]]

Why use HugePages?

How to use HugePages?

If you want to use HugePages you have to do both of the steps below if you compile yourself.

Self compiled applications

  • During Compilation
    • one of the craype-hugepages<size> (i.e. craype-hugepages16M) modules has to be loaded.
    • This will link the hugepages library to your application.
  • During runtime
    • Load the craype-hugepages module with the pagesize you want to use.
    • The size chosen during runtime is completely independent from the size you have chosen during compilation.
    • Therefore you can compile once and test different sizes during runtime without changing the binary.



precompiled, dynamically linked applications