ko1 (Koichi Sasada) wrote in #note-8: > If it returns `[]` always, I think we don't need to introduce it. I've updated pr. The limit parameter behaves as fallow: 1. ```limit == nil```: returns all messages in the queue, or blocks if...synacker (Mikhail Milovidov)
ko1 (Koichi Sasada) wrote in #note-8: > For this purpose, it is possible to introduce another parameter such as `timeout: 0`. > ... LGTM, I’ll update the PR with this suggestion.synacker (Mikhail Milovidov)
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)
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)
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)
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)
**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)
* [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)
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)
synacker (Mikhail Milovidov)09:56 PM Ruby Feature #21869: Add receive_all Method to Ractor API for Message Batching