@SercoSteveB wrote:
How about having two Queues; Queue#1 from Producer to Consumer Loop 1 and Queue#2 from Consumer Loop 1 to Consumer Loop 2. As elements arrive at Consumer Loop 1 (on Queue#1) they are dequeued for use in Consumer Loop 1 but also enqueued onto Queue#2 for use in Consumer Loop 2?
Yes, that's a fairly common solution. E.g. any action taking >100ms should be offloaded to a 2nd queue as to not bog down the first consumer.