You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When run TPUs, jax prints a warning at startup unless /sys/kernel/mm/transparent_hugepage/enabled is set to always (as of 5cb2994).
Is there a reason that madvise does not suffice? madvise is the default on a number of distro kernels, and should still allow libtpu to benefit from transparent hugepages by making the appropriate madvise(…, MADV_HUGEPAGE) call. Moreover, always has a long history of performance issues and causing high memory overhead due to fragmentation.
Is madvise actually insufficient for the necessary optimizations in jax/XLA/libtpu?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When run TPUs,
jaxprints a warning at startup unless/sys/kernel/mm/transparent_hugepage/enabledis set toalways(as of 5cb2994).Is there a reason that
madvisedoes not suffice?madviseis the default on a number of distro kernels, and should still allow libtpu to benefit from transparent hugepages by making the appropriatemadvise(…, MADV_HUGEPAGE)call. Moreover,alwayshas a long history of performance issues and causing high memory overhead due to fragmentation.Is
madviseactually insufficient for the necessary optimizations in jax/XLA/libtpu?Beta Was this translation helpful? Give feedback.
All reactions