Enforcing maximum number of threads consumed by a worker on a per job basis

Ongoing

Robert Choquette

• December 13, 2021 20:44

We are operating a cluster as a shared resource on our team and we are noticing that some jobs are taking a long time and holding resources. We would like to be able to set a max threads limit on a per-job basis so that we can ensure other solves get through the queue while the large one is still working. Is this possible to do on the server side, or is it up to the client to set a max threads parameter?

Thanks for your help,

0

• Official comment

  

  Simranjit Kaur

  Gurobi Staff

  • December 06, 2024 00:22

  This post is more than three years old. Some information may not be up to date. For current information, please check the Gurobi Documentation or Knowledge Base. If you need more help, please create a new post in the community forum. Or why not try our AI Gurobot?.
• 

  Simon Bowly

  Gurobi Staff

  • December 14, 2021 04:30

  Hi Robert,

  You can use the THREADLIMIT parameter on the server side to control this. This sets the default limit on the number of threads used by a worker launched on the cluster to handle a single optimization job. This overrides the setting of the Threads parameter on the client side, so the number of threads used by a single job would be the smaller of these two values.

  See the configuration properties section of the documentation for full details of this parameter. These configuration parameters can be set in the grb_rs.cnf file.

  Best regards,
  Simon

  0

Post is closed for comments.