Replies: 1 comment 2 replies
-
|
@drewbaker this type of strategy is very complicated to implement. There are many strategies, like round robin, idle time, load balancing. We intend to provide multiple strategies on Sidequest Pro. For now, what you can do is to put all queues with the same priority. Then the jobs will be picked in order they are inserted. You can also change the queue priority during runtime, so you can implement your own strategy if you like by fiddling with the queues priorities. Look for |
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.
-
Currently it seems jobs come off the top of the queue... That makes sense.
But, I have a problem where the queue will get blocked by group of tasks for a single user, when I'd like to spread it out among all active users. Seems like the easiest solution to this is to allow the jobs to get pulled from the queue at random?
For example, lets say you have a bunch of packages to send out of the warehouse. One customer "A" comes in and buys 1000 packages... And then another customer "B" comes in and buys 1 package.
Should B have to wait until all of A? Ideally no.
The best solution would be a way to load balance jobs based on some config, but I'd settle with random order of jobs in the queue.
Beta Was this translation helpful? Give feedback.
All reactions