The idea that led me to try transparent_hugepage came from another piece
of evidence I forgot to mention.  I noticed that half of my RAM, 1GB,
was consumed by anonymous page allocations.  Transparent_hugepage,
through khugepaged, defragments AND merges the 4k anonymous pages into
hugepages.  I figured that it would be far better to have a few hundred
2MB pages to reduce the overhead of context switches.  It seems the
savings of 60MB in reduced page tables, and its seemingly miraculous
return to the living, is all the evidence needed.  My system is now
chugging along with roughly 400MB of hugepages, at any given time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159258

Title:
  The IOSCHED default of deadline combined with 4k page size causes poor
  performance in lightly configured systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159258/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to