Replies: 1 comment 2 replies
-
Hey @northopn I am a new maintainer of Shoryouken. Please give me few days to analyze this 🙏 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I ran an experiment between these Shoryuken's configs with 3 queues/workers.
1. Separate groups.
2. WRR group
I ran K6 to test against both configs and I found an odd result. please check below. because in my mind I thought using a workers pool would give a better result.
K6 script scenario I used was publishing queue-message to all queues with ramping-up rate for 10mins.
Here are the results
Separate group

with this config, the consumer processes the messages almost instantly once the message is landed on the queue. and the oldest message's average time is 30 seconds
WRR

with this config, I spent almost 40mins to finish up. and the oldest message in the queue was an hour.
The worker code
please give me advice. I can provide more info if needed
Beta Was this translation helpful? Give feedback.
All reactions