|
|
|
|
View Forum Thread
Anyone can view the forums, but you need to log in in order to post messages.
> Forum Home >
Support >
Smedge 2015.2 odd priority behaviour
|
|
Wed, 06/Apr/2016 1:36 PM |
Mark
8 Posts
|
Hi All
Within the Master Options we have:
If work priority is the same - First In, First Out
Global Priority Boost - 0 Packets
Pool Priority - Always use the job priority, ignoring pool priority.
We have not yet got into anything that I know of that would alter the priority other than the actual priority setting. Routinely we set priority 49 and everything else revolves around that. So...
Any idea why a job submitted minutes or hours later will take over the farm? There seems to be little rhyme or reason. At the moment the only way to manage it is to specifically make newer jobs a lower priority than older ones.
Hope someone can point out my obvious misstep.
Best regards
Mark
|
| |
|
|
|
Thu, 14/Apr/2016 4:34 PM |
Robin
1138 Posts
|
Check that the job itself is not getting a manual priority boost, in the advanced info tab.
Otherwise, please contact me at support if you can reproduce, and send logs from the master.
|
| |
|
|
|
|
. |
