Bug Report - High Memory Usage when Providing Float to Concurrency

[abdeljalil09]

Description:
I encountered an issue while using the Bull.js module in Nest.js. When I provided a float value (5 / 2, which is 2.5) to the concurrency property in the processors configuration, I noticed a significant increase in memory usage.

Expected Behavior:
The concurrency value should be rounded to the nearest integer, as is the common practice in similar scenarios.

Steps to reproduce
Actual Results:
Upon providing 5 / 2 as the value for concurrency, the memory usage increases significantly, causing potential performance and stability issues.

Expected behavior
I would expect the concurrency value to be rounded to the nearest integer, resulting in a value of 3 in this case (Math.round(5 / 2)).

[manast]

I think it is better to throw an exception in this case actually.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.