> > > > > > What impact would there be if ThreadPriority.Lowest was set for all of > the other executor threads? > > I'm guessing that based upon the current design, the Manager would see > the Executor disappearing as non-Alchemi processing on that machine > increased. > > I think it would make sense to have a heartbeat thread operate at > ThreadPriority.Normal or AboveNormal, but to decrease the priority of > all other threads to Lowest or BelowNormal. I don't think there > should be a GUI for this, but it should be editable in the Executor's > config file. > > That way, the Executor has less impact on the machine, but never > actually drops off the grid.
This makes sense :). This feature would fit in better if the Manager would be more tolerant to disappearing/reappearing Executors. OTOH do we really need the heartbeat thread? It surely generates a lot of chatter on the network. Why not make the Manager take an optimistic view of life and assume that all Executors are alive until proven otherwise by a failed communication? Tibor ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ alchemi-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alchemi-users
