NC scheduling policy

  • theklink
Posted: Wed, 10/14/2009 - 11:16

Andrea,

Remember when we met and you mentioned changing the default scheduling policy for NC?
(The problem where small jobs will be scheduled on the least busy slave (A), and then a large job comes in which can only be run on (A), and it has to be queued). Assume A has one slot capacity, for the sake of this example.

My question is whether that behavior will be addressed (or configurable) in your next release.

Thanks!

--Jon

Jon M. Klinkefus, Sr. Electrical Engineer
EDA Support
jmklinke@rockwellcollins.com
VPN 319-295-7096

‹ Resources pane on project page. Slave Exit Information (Enhancement Idea) ›

Klink, Sorry for allowing

  • btjanes
  • 05/08/09
  • Tue, 12/08/2009 - 08:42
  • Copy comment link

Klink,

Sorry for allowing this one to slip be unreplied to. We do not have anything in our upcoming release to handle this situation specifically. Our current recommendation is to use job classes for small/big jobs, and possibly assigning a default job class, to handle this so that big jobs must explicitly request a slave that handles big jobs. I believe you guys currently have a "critical" job class that already does this somewhat. We do have in our ticket system a ticket for providing some level of scheduler customizability, but it's not current scheduled for a release.

Brian