I understand the concept of sleep or delay are for good reasons frown upon by the Erlang community. Process.send_after/4 is an excellent alternative in most cases and allows for maximum 1ms precision (so does the underlying Erlang erlang:send_after call). Yet, 1ms is an eternity for my application. …

That doesn’t answer your question in a satisfying way but at least it contains an explanation: [erlang-questions] Minimum time for timer:sleep()? There’s an Erlang module code proposed several answers later but I am not seeing it addressing microsecond delays …

[image] dimitarvp: Finally, I am not very convinced you should even use Erlang / Elixir if your app has such needs. +1 [erlang-questions] What does “soft” real-time mean?

As to the link: That would stand in 2007, but POSIX implementation of the time module has been rewritten since and allows for much higher precision and fine-tuning. You can always use :timer.tc and implement your own loop of course (using :erlang.yield ) Busy loop is not an option once I need 10…

I partially understand your motivation. I can’t speak for Erlang’s creators but in my eyes they opted for the lesser evil – namely being realistic they cannot offer those features due to varieties in all kernels where the BEAM must work. If you work on a soft real-time system then I would say that …

RE: Custom scheduler, better don’t. In my opinion anyway, not a strictly factual advice. IMHO: I believe the 1ms resolution stems from above mentioned soft-realtimedness. To my knowledge, the scheduler does regular checks against system time ( erlang time with ns resolution) and forwards the messa…

I believe the 1ms resolution is the lowest common (reliable) denominator of all the platforms the BEAM runs on. It’s possible to go use a much smaller resolution on most platforms, but not all of them, unfortunately.

shameless plug I wrote a library with the same api of :timer but with a resolution in microseconds it’s called micro_timer [image] devonestes: I believe the 1ms resolution is the lowest common (reliable) denominator of all the platforms the BEAM runs on. It’s possible to go use a much smaller…

erts_milli_sleep is only used in testing and on operating systems without a monotonic time source. What is used to sleep is either futex or WaitForSingleObject with some spinning done around it. This is the relevant code for unix: otp/erts/lib_src/pthread/ethr_event.c at master · erlang/otp · GitH…

Thanks for the clarification! I was looking exactly for that, you saved me a lot of work! My use case was correctness, I needed to generate exactly 60fps (or 90fps, or 120fps) and it can’t be accomplished with ms alone. My implementation is very naive, it’s ok if you have few timers running and d…

Kudos for sharing your expert knowledge with us @garazdawi Is there an example how to use timerfd_create to increase the resolution? What would it encompass to implement the erlang:send_after(Time, Dest, Msg, Unit, Options) function where Unit is the Erlang time_unit() ? From what I gathered from e…