Actions
Feature #21121
openRactor channels
Status:
Open
Assignee:
-
Target version:
-
Description
Motivation:¶
It would be nice be able to Ractor.yield
in a non-blocking way. Right now a Ractor.yield
blocks until another ractor calls r.take
on the yielding ractor.
This is bad in the following scenario:
main = Ractor.current
rs = 10.times.map do
Ractor.new(main) do |m|
ret = []
loop do
# do a bunch of work that takes a while, then:
begin
obj = m.take
rescue Ractor::ClosedError
end
if obj
ret << obj
else
break
end
end
ret
end
end
50.times do |i|
Ractor.yield(i) # this will block until some ractor calls take on us, but it could be a while if there is processing before the `take` call.
end
main.close_outgoing
# Ideally, we could do some work in main ractor that takes some time while the other ractors do their processing. But we're blocking right now
# during all the calls to `Ractor.yield`.
# Finally, get the results
while rs.any?
r, obj = Ractor.select(*rs)
$stderr.puts "Ractor #{r} got #{obj}"
rs.delete(r)
end
I'd like other ractors to be able to do work in a "fire and forget" kind of way. It isn't possible right now due to the limitations of Ractor.yield
and Ractor#take
.
What we need is some kind of yield
buffer so the yielder doesn't block. I propose that Ractor channels would allow this type of programming to work.
Example using channels:¶
chan = Ractor::Channel.new # We could specify buffer size like Go or it could be dynamically growable
rs = 10.times.map do
Ractor.new(chan) do |c|
ret = []
loop do
obj, _closed = c.receive # returns `[nil, true]` if `c` is closed and its buffer is empty. It blocks if the buffer is empty and `c` is not closed.
if obj
ret << obj
else
break
end
end
ret
end
end
50.times do |i|
chan.send(i) # non-blocking, fills a buffer and only wakes a receiver if there is one
end
chan.close
# Do some processing while ractors do their work.
# Then, collect the results
while rs.any?
r, obj = Ractor.select(*rs)
puts "Ractor #{r} got #{obj}"
rs.delete(r)
end
With an API similar to this, we could have "fire and forget" processing with ractors.
Actions
Like1
Like0Like0Like0