You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use one of the DB or file Storage methods that all the workers can read from then it would work. As each would call from that. So decided where your workers are on same server, network, internet etc. I’ve used Redis for this before. (As each worker checks the same time left token, just think about how many workers and a time locking them if the timeout checking the worker kills it before it gets all its token use work done) — for this sometimes I have made more tokens with less quota for a group of workers, then say 2x5 workers with 10 token each might be better than 10 with 20 token. You need to test and see when all busy.
My use case is :
Would this repo implementation be fine with this distributed constraint ?
Would this rate of 10 be an absolute limit or an average ?
The text was updated successfully, but these errors were encountered: