[HN Gopher] Deep Diving into the Erlang Scheduler
       ___________________________________________________________________
        
       Deep Diving into the Erlang Scheduler
        
       Author : unripe_syntax
       Score  : 54 points
       Date   : 2024-04-23 09:22 UTC (1 days ago)
        
 (HTM) web link (blog.appsignal.com)
 (TXT) w3m dump (blog.appsignal.com)
        
       | alakra wrote:
       | Somewhat related, does anyone know the difference between
       | `erlang:suspend_process` and `sys:suspend` when trying trying to
       | "unschedule" a process for executing reductions? Are they the
       | same thing?
        
       | uticus wrote:
       | > The idea of "reduction" in Erlang is inherited from its Prolog
       | ancestry. In Prolog, every execution step is termed a goal-
       | reduction, involving breaking down a logic problem into
       | individual components and solving each part accordingly.
       | 
       | > To promote fairness among processes, Erlang's preemptive
       | scheduling relies on reductions rather than time slices. If a
       | process exhausts its allocated reductions, it can be preempted,
       | even if its execution isn't complete.
       | 
       | Fascinating
        
       ___________________________________________________________________
       (page generated 2024-04-24 23:02 UTC)