synacker (Mikhail Milovidov)

	open	closed	Total
Assigned issues	0	0	0
Reported issues	1	1	2

09:42 AM Ruby Feature #21930: Add Ractor#empty? method to check for pending messages without blocking: nobu (Nobuyoshi Nakada) wrote in #note-8:
> synacker (Mikhail Milovidov) wrote in #note-4:
> ...
Thank you for the feedback. Ractor#empty? isn’t a niche fix - it’s a general‑purpose primitive for efficient schedulers and Ractor‑Fiber i... synacker (Mikhail Milovidov)

09:47 PM Ruby Feature #21930: Add Ractor#empty? method to check for pending messages without blocking: ufuk (Ufuk Kayserilioglu) wrote in #note-6:
> @synacker Which version of Ruby are you testing with? Can you please send your `ruby -v` output for the benchmark results?
This is a ruby version from my pr (https://github.com/ruby/ruby/... synacker (Mikhail Milovidov)
08:41 PM Ruby Feature #21930: Add Ractor#empty? method to check for pending messages without blocking: nobu (Nobuyoshi Nakada) wrote in #note-3:
> As for your example, why does `Worker` ractor handle both of `main_task` and dispatch alone, instead of launching each ractors?
I compared two strategies for handling concurrent tasks:
1... synacker (Mikhail Milovidov)

09:32 AM Ruby Feature #21930: Add Ractor#empty? method to check for pending messages without blocking: nobu (Nobuyoshi Nakada) wrote in #note-3:
> This sounds like leading to a typical TOC/TOU problem.
I appreciate the concern about a potential TOC/TOU issue, but I believe it doesn’t apply in this specific case. Consider the following pa... synacker (Mikhail Milovidov)

06:42 PM Ruby Feature #21930: Add Ractor#empty? method to check for pending messages without blocking: Added pr: https://github.com/ruby/ruby/pull/16277 synacker (Mikhail Milovidov)
06:20 PM Ruby Feature #21930 (Feedback): Add Ractor#empty? method to check for pending messages without blocking: **Summary**
In concurrent Ractor‑based architectures, there’s a critical need to check whether a Ractor has pending messages without blocking. Currently, this is not possible with the standard API
**Motivation**
The Ractor API provi... synacker (Mikhail Milovidov)

12:23 PM Ruby Misc #21877: DevMeeting-2026-03-17: * [Feature #21869] Add receive_all Method to Ractor API for Message Batching
* This feature is essential for high‑load services because message batching is a highly efficient technique for reducing the number of expensive I/O requests ... synacker (Mikhail Milovidov)

01:14 PM Ruby Feature #21869: Add receive_all Method to Ractor API for Message Batching: Eregon (Benoit Daloze) wrote in #note-3:
> Is it? In your example you call `file.write` for each message in both cases.
> ...
This is also a realistic scenario. To guarantee messages are saved to file, you'd normally need to call ```fl... synacker (Mikhail Milovidov)
12:11 PM Ruby Feature #21869: Add receive_all Method to Ractor API for Message Batching: ko1 (Koichi Sasada) wrote in #note-2:
> Does it block when the queue is empty or returns \[\]? (I think the example expects blocking)
Yes, it blocks if the queue empty. The method ```receive_all``` accepts a limit parameter:
1. ```limit... synacker (Mikhail Milovidov)

10:41 PM Ruby Feature #21869: Add receive_all Method to Ractor API for Message Batching: PR in github: https://github.com/ruby/ruby/pull/16105 synacker (Mikhail Milovidov)

Also available in: Atom

Ruby Issue Tracking System