DPDK has two hugepage sizes:2MB hugepages and 1GB hugepages. I run the command below to use the 1GB hugepages: However, when I run the command cat /proc/meminfo: It still seems to use the 2MB hugepages. What should I do to use the 1GB hugepages? Answer The Hugepagesize field of /proc/meminfo is the default huge page size used by applications allocating
Tag: huge-pages
JDK 1.8 -XX:+UseLargePages behavior when there’s not enough huge pages left on os
I am currently confusing how to optimize using HugePages with JVM applications with Netty, -XX:+UseLargePages option enabled, and using G1Gc. Also, I didn’t forget to set the same max and min size of the heap and metaspace. My application looks fine, but I was wondering what happens if there’s no remaining free huge pages on system since JVM uses additional
How does the memory behind statically allocated huge pages get distributed across NUMA nodes?
In my /etc/default/grub file I have explicitly set aside N huge pages with “hugepages=N”. If I’m running on a box with 2 NUMA nodes, does N/2 huge pages get set aside for each node, or do they all go to node 0, or ….? Also is there a way on the command line to query how they’re split across nodes?
Can’t Write to /sys/kernel/ to disable Transparent Huge Pages (THP) for MongoDB on OVH CentOS 7
My Issue I am having trouble removing MongoDB warnings about Transparent Huge Pages (THP) on an OVH CentOS 7 installation, and the issue appears to be the inability to write to /sys/kernel/mm as root. First, I realize the OVH kernel is customized, and I know many of you will say to go with a fresh non-customized kernel, but that’s not