Messages in this thread | | | From | "Luck, Tony" <> | Subject | RE: [RESEND PATCH v2 1/4] mm/hwpoison: fix traverse hugetlbfs page to avoid printk flood | Date | Tue, 17 Sep 2013 16:47:39 +0000 |
| |
> Transparent huge pages are not helpful for DB workload which there is a lot of > shared memory
Hmm. Perhaps they should be. If a database allocates most[1] of the memory on a machine to a shared memory segment - that *ought* to be a candidate for using transparent huge pages. Now that we have them they seem a better choice (much more flexibility) than hugetlbfs.
-Tony
[1] I've been told that it is normal to configure over 95% of physical memory to the shared memory region to run a particular transaction based benchmark with one commercial data base application.
| |