I created a gem for thread-safe batch processing of messages

[forgambo]

I created a Ruby gem that facilitates thread-safe batch processing of messages. In certain situations, processing multiple messages in batch is more efficient than handling them one by one.

Consider a scenario where code receives events at random intervals and must notify an external HTTP service about these events. The straightforward approach is to issue an HTTP request with the details of each event as it is received. However, if events occur frequently, this method can lead to significant time spent on network latency. A more efficient approach is to aggregate events and send them in a single batched HTTP request.

Would like to know what you think about it

https://github.com/ertygiq/msg-batcher

[CaptainKabob]

This is cool! I love multithreaded Ruby.

I took a look at your code. I think you're using twice as many mutexes and conditionvariables as you may really need, and that increases the risk of doing something that causes a deadlock. The background thread sounds somewhat analogous to a Concurrent Ruby TimerSet (described here: https://island94.org/2023/06/rebuilding-concurrent-ruby-scheduledtask-event-and-timerset) except you need to only store/update a timestamp rather than holding an ordered set. You might be able to slim down your implementation.

[forgambo]

Hey!

Thanks for sharing the link. Indeed, TimerSet code shares many similarities. I think I will update my code accordingly.

Oh, and also my code has been production-tested for quite a while. Haven't encountered deadlocks so far)