synacker (Mikhail Milovidov)
- Login: synacker
- Registered on: 01/22/2026
- Last sign in: 02/10/2026
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 1 | 0 | 1 |
Activity
02/13/2026
-
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 ...
02/10/2026
-
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... -
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...
02/07/2026
-
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
-
08:52 PM Ruby Feature #21869 (Open): Add receive_all Method to Ractor API for Message Batching
- **Summary**
The Ractor API provides an excellent mechanism for inter‑thread communication, but it currently lacks a built‑in message batching technique. I propose adding a receive_all method to enable batch processing of messages, which...