WiredTiger should support huge pages in the read path, and possibly in the write path (pages in the write path are discarded quickly).

> This also reminds me: I never sent you a note on huge pages. Huge pages reduce the impact of memory address lookups when translating from virtual -> physical addresses. To use them on Linux, memory needs to be allocated as a shared memory segment; Oracle does this, as does MySQL. One nice side-benefit is that huge pages can't currently be swapped, so it effectively pins memory in memory – this becomes hugely important we're still on a relatively old version of the linux kernel which has unfortunate behavior for swap.

Linux is moving to "transparent huge pages", which may or may not yet be fully integrated into the page cache.

There probably needs to be a configuration to WiredTiger which is how many huge pages it can use, there's currently a global limit for Linux.