Manuel Astudillo
Manuel Astudillo
> Whenever there is a spike, worker processes are created, and they never finish/close. This makes the BullMQ deployment leak memory until we restart the docker image. Why would this...
Btw, something to consider, if the jobs are very CPU intensive, you should not use a larger concurrency factor than your actual CPU cores, because that would just add overhead...
> Each queue is configured with a high concurrency factor to handle load spikes. Once the spike is done the isolated workers are not finished, thus from my POV that...
For instance, if you want to just define a subset of valid job names, you could create a type like: ``` type MyJobNames = "foo" | "bar" | "baz"; ```...
I think the important here is that bullmq-otel adheres to Otel conventions, but having a generic naming of attributes that is not tied specifically to Otel in BullMQ as we...
Yes, we are missing some proxies for flow related methods in Flows. Thanks for reporting.
We have a PR for this, seems like it could be merged anytime now https://github.com/taskforcesh/bullmq/pull/1417
Added in v5.35.0: https://docs.bullmq.io/changelog#id-5.35.0-2025-01-22
The easiest way would be to configure it via env variables.
If the call takes too long time thats not good in general. We may need to add pagination support to keep the calls very fast, as keeping Redis busy with...