Implementing a synchronization barrier in Ruby

后端 未结 2 1837
死守一世寂寞
死守一世寂寞 2021-01-02 10:56

I\'m trying to \"replicate\" the behaviour of CUDA\'s __synchtreads() function in Ruby. Specifically, I have a set of N threads that need to execut

相关标签:
2条回答
  • 2021-01-02 11:35

    There might be merits of having the threads wait for each other. But I think that it is cleaner to have the threads actually finish at "midpoint", because your question obviously impliest that the threads need each others' results at the "midpoint". Clean design solution would be to let them finish, deliver the result of their work, and start a brand new set of threads based on these.

    0 讨论(0)
  • 2021-01-02 11:36

    Let's implement a synchronization barrier. It has to know the number of threads it will handle, n, up front. During first n - 1 calls to sync the barrier will cause a calling thread to wait. The call number n will wake all threads up.

    class Barrier
      def initialize(count)
        @mutex = Mutex.new
        @cond = ConditionVariable.new
        @count = count
      end
    
      def sync
        @mutex.synchronize do
          @count -= 1
          if @count > 0
            @cond.wait @mutex
          else
            @cond.broadcast
          end
        end
      end
    end
    

    Whole body of sync is a critical section, i.e. it cannot be executed by two threads concurrently. Hence the call to Mutex#synchronize.

    When the decreased value of @count is positive the thread is frozen. Passing the mutex as an argument to the call to ConditionVariable#wait is critical to prevent deadlocks. It causes the mutex to be unlocked before freezing the thread.

    A simple experiment starts 1k threads and makes them add elements to an array. Firstly they add zeros, then they synchronize and add ones. The expected result is a sorted array with 2k elements, of which 1k are zeros and 1k are ones.

    mtx = Mutex.new
    arr = []
    num = 1000
    barrier = Barrier.new num
    num.times.map do
      Thread.start do
        mtx.synchronize { arr << 0 }
        barrier.sync
        mtx.synchronize { arr << 1 }
      end
    end .map &:join;
    # Prints true. See it break by deleting `barrier.sync`.
    puts [
      arr.sort == arr,
      arr.count == 2 * num,
      arr.count(&:zero?) == num,
      arr.uniq == [0, 1],
    ].all?
    

    As a matter of fact, there's a gem named barrier which does exactly what I described above.

    On a final note, don't use sleep for waiting in such circumstances. It's called busy waiting and is considered a bad practice.

    0 讨论(0)
提交回复
热议问题