Node prioroty ignored

Viewing 6 posts - 1 through 6 (of 6 total)
  • Back to forum
    Posted in: Muster usage
  • Mike Thomson
    12th March 2007 at 10:25 pm #14164

    It seems that muster dispatcher is ignoring node priorities. We have set our fast machines to have a node priority of 10, and our slower machines are set lower all the way down to 1. In muster explorer, they all come up as either 1 or 2, and priority seems to be ignored. When we submit renders, it seems any random machine will pick up the renders, not in the node priority order.

    Muster 5.1, Win XP.

    Thanks,

    Mike

    Atmosphere-Nik
    16th March 2007 at 8:52 pm #14623

    RightClick on render node in the Host Instance window and go to: set process priority… Set your faster machines to Realtime and slower to high and even slower to normal etc…

    Hope this works,

    – Nik

    Leonardo Bernardini
    17th March 2007 at 8:17 pm #14629

    I think Mike is talking about the selection priority of the nodes. I’ll take a look over this and see if there’s something that’s not working as intended.

    Mike Thomson
    4th April 2007 at 2:19 am #14638

    That’s right. If all machines are idle, and we submit a job, the slower computers usually pick up the renders, rather than our faster ones.

    Leonardo Bernardini
    5th April 2007 at 3:11 pm #14639

    This means that they are selected in a reverse order ? This could change the problem. Knowing if it’s working reversed or not working at all can help us in detecting the source of the issue.

    Leonardo Bernardini
    22nd May 2007 at 12:22 am #14667

    Issue fixed in version 5.2

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.