-
Hi, I am testing the features of your projects for application to my company project. As I am modifying the configurable properties, I found this comments on the properties in
I want to know if the comments are written right.
According to comment above, the expected behaviour is:
But it actually does not work like that. No matter how many jobs I schedule, backgroundJobrunrServer always ends up enqueuing all the existing scheduled jobs in single poll interval. These are mysql DB logs. As you can see, all 20 jobs are enqueued within a minute.
and this is debug log from application server.
I don't think the comment is describing the properties right, so I wonder if it is a bug or just not written right. Or, maybe my configurations are wrong? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I think the docs are indeed not 💯 % clear. It's the amount of jobs that are fetched per database round-trip. Some companies / developers use it to optimize throughput. We will update our docs to make it clearer. JobRunr Pro v7 will support rate limiting and allows you to limit the amount of enqueued jobs (using concurrent rate limiter or sliding time window rate limiter). |
Beta Was this translation helpful? Give feedback.
I think the docs are indeed not 💯 % clear. It's the amount of jobs that are fetched per database round-trip. Some companies / developers use it to optimize throughput. We will update our docs to make it clearer.
JobRunr Pro v7 will support rate limiting and allows you to limit the amount of enqueued jobs (using concurrent rate limiter or sliding time window rate limiter).