On Sunday, 20 February 2022 at 17:58:41 UTC, Ali Çehreli wrote:
Another one is to set the message box sizes to throttle.
Message sizes and rates are relatively well know so it will be
easy to pick a throttle point that's unlikely to backup the
source yet provide for some quick DB maintenance in the middle
of a testing session.
In case you haven't seen yet, the recipe for std.concurrency
that works for me is summarized here:
https://www.youtube.com/watch?v=dRORNQIB2wA&t=1735s
Thanks! I like your simple exception wrapping pattern, will use
that.
