Hi, Just sort it out from job.c. Please correct me if my understanding is wrong: low pri value tasks are always dispatched early than high pri tasks, no matter how late it is added, same pri value tasks are dispatched in putting order, FIFO. (in same tube) thanks.
On Dec 9, 2:50 am, Linan <[EMAIL PROTECTED]> wrote: > hi, > Thanks for the quick response. I understand the lower priority value = > higher priority, but no idea how it the sequence is calculated. > which factor is more important, pri or putting-sequence? is the next > job = min(pri*job.id)? > > On Dec 9, 2:28 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > > > > > On Mon, Dec 8, 2008 at 8:25 PM, Linan <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > Basically I have three groups of tasks for different type of users, > > > normal, paid users, and enterprise users. The workers are same. The > > > only difference is enterprise users have highest priority, then paid > > > users and lastly normal users. So if it's possible for me to watch a > > > tube and pick up tasks from enterprise users first, no matter how late > > > they are added? I tried setting pri, but not clear how it will affect > > > the dispatching sequence. Can anybody explain to me how it works? > > > Yes. Lower numbers are higher priority, with 0 (or maybe it's 1?) > > being top (i.e. soonest) priority. > > Priority can be a full integer range, so you can decide how best to > > make priority groupings. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
