Interesting how on this Linux box, scheduling NOPs like nanosleep of 0 and futex waiting on an already set memory location … both take around 60 microseconds, cannot afford to do many of those per millisecond.

Source

• URL: https://x.com/NOTimothyLottes/status/2065840191340707905
• Author: NOTimothyLottes (@NOTimothyLottes)
• Posted: 2026-06-13 16:54:17

Thread

1/ @NOTimothyLottes

Interesting how on this Linux box, scheduling NOPs like nanosleep of 0 and futex waiting on an already set memory location … both take around 60 microseconds, cannot afford to do many of those per millisecond. Food for thought for high fps targets

Branches: 2026-06-13-rflaherty71-seems-like-people-trying-to-push-high-frame-rates, 2026-06-13-raggi-nanosleep-0-will-sleep-for-the-timer-slack-mm, 2026-06-13-winning_tactic-why-not-do-a-gradual-sleeping-start-with-while, 2026-06-13-BonbliStar-most-futex-impls-ive-seen-check-for-that-and

2/ @NOTimothyLottes

A write of zero bytes is closer to say 6 microseconds in contrast, so just the user/kernel transition is expensive but 10x faster