Manuel Astudillo

you don't need to do anything special, with a standard redis deploy on modern hardware and increasing parallelism of 1 worker (concurrency 200 or more for example) you can achieve...

The hash tag will always be needed, the other question is if ioredis works correctly or not, but I think some people has been successful running cluster with bull lately...

First, I think it is pretty strange that you got 400% slower performance, it would be interesting if you can isolate in a simple case such performance disparity so that...

If by workaround you mean dividing your jobs into different queues so that they can be assigned to different shards, then the answer is no, we will not do this...

This issue comes from this other issue in IORedis: https://github.com/redis/ioredis/issues/1830 The only workaround I know of right now is to just ignore the "end" event... strangely, I am quite sure...

This is actually working perfectly using NodeJS instead of Bun. For some reason, I started reproducing the issue with Bun and forgot about it. I am trying with version 18.10.0...

@ajimix because that is the way it is designed in order to obtain a robust repeatable job functionality. The next job that is going to be repeated is always created...