3 ms·

> It will be more interesting to talk about those applications if and when they are found. Redis recommend disabling hugepages: https://redis.io/docs/latest/op

> It will be more interesting to talk about those applications if and when they are found. Redis recommend disabling hugepages: https://redis.io/docs/latest/operate/oss_and_stack/management/optimization/latency/#latency-induced-by-transparent-huge-pages https://redis.io/docs/latest/operate/oss_and_stack/managemen... --- Actually, looks like they changed the log warning to be more specific, as it's just the "always" setting which seems to cause Redis grief? https://github.com/redis/redis/issues/3895 https://github.com/redis/redis/issues/3895

scottlamb 7mo ago
By "those applications" I'm talking about other applications affected by this regression. There are several apps in addition to Redis that recommend limiting the transparent huge page configuration. (Some of them recommend using explicit huge pages instead.) But it's quite possible none of them are affected by this regression, as it may be particular to apps using spinlocks. (Certainly the new rseq API mentioned in the thread is targeted at spinlock users.) It seems equally possible to me that some spinlock-using app has a regression irrespective of huge pages.