Gurobi cannot exploit more than 32 cores of machine
進行中I have some attempts to solve a scheduling problem using the Gurobi in python and .NET on Ubuntu-server installed on a hyper-computing cluster with 64 physical cores. Unfortunately, both solvers cannot exploit more than 32 cores and it seems a bit weird to me! Even I attempted to force using 64 cores with the Threads parameter; however, it deteriorated the convergences speed. Appreciate someone has any interpretations of this case and of course a solution to this issue.
The machine is deployed with 64 physical cores. Here is the detail of the core #26:
*-cpu:25
description: CPU
product: Intel(R) Xeon(R) CPU E5-2698 v4 @ 2.20GHz
vendor: Intel Corp.
physical id: 419
bus info: cpu@25
version: RHEL 7.6.0 PC (i440FX + PIIX, 1996)
slot: CPU19
size: 2GHz
capacity: 2GHz
width: 64 bits
and core #64:
*-cpu:63
description: CPU
product: Intel(R) Xeon(R) CPU E5-2698 v4 @ 2.20GHz
vendor: Intel Corp.
physical id: 43f
bus info: cpu@63
version: RHEL 7.6.0 PC (i440FX + PIIX, 1996)
slot: CPU3f
size: 2GHz
capacity: 2GHz
width: 64 bits
-
正式なコメント
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?. -
Note that this is cross-posted in OR Stack Exchange: https://or.stackexchange.com/questions/5416/gurobi-and-cplex-cannot-exploit-more-than-32-cores-of-machine
1 -
Yes, indeed. I couldn't get a reasonable answer; So, I also posted here.
0
投稿コメントは受け付けていません。
コメント
3件のコメント