Error termination of barrier method for a large LP problem
回答済み
I am dealing with a large LP problem. The python gurobi api halted with an error below. The API is still running after this error showing but it can not output any other results.
Can anyone give me some ideas about this?
-
正式なコメント
-
Gurobi Staff
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?. -
-
-
Hi,
I created a ticket request for this issue. Please proceed there.
Best regards,
Jaromił1 -
-
Hi,
I seem to be getting the same error for a MIP in Gurobi 9.1 through the Java API. Are there any updates concerning what caused this issue? I observed a spike in the memory consumption (basically 100% utilization) just before the error.
Best regards,
Martin
Gurobi Optimizer version 9.1.0 build v9.1.0rc0 (win64)
Thread count: 8 physical cores, 16 logical processors, using up to 16 threads
Optimize a model with 6011135 rows, 693100 columns and 37863968 nonzeros
Model fingerprint: 0x9095ad64
Variable types: 330 continuous, 692770 integer (692770 binary)
Coefficient statistics:
Matrix range [2e-01, 1e+00]
Objective range [1e+00, 1e+00]
Bounds range [1e+00, 4e+02]
RHS range [1e+00, 1e+01]
Presolve removed 51224 rows and 0 columns (presolve time = 6s) ...
Presolve removed 2629584 rows and 0 columns (presolve time = 13s) ...
Presolve removed 2629721 rows and 137 columns (presolve time = 20s) ...
Presolve removed 2629721 rows and 137 columns (presolve time = 20s) ...
Presolve removed 2629721 rows and 137 columns (presolve time = 26s) ...
Presolve removed 4678698 rows and 137 columns (presolve time = 30s) ...
Presolve removed 4755101 rows and 137 columns (presolve time = 35s) ...
Presolve removed 4803573 rows and 137 columns (presolve time = 40s) ...
Presolve removed 4803573 rows and 137 columns (presolve time = 45s) ...
Presolve removed 4803573 rows and 137 columns (presolve time = 50s) ...
Presolve removed 4803573 rows and 137 columns (presolve time = 55s) ...
Presolve removed 4807997 rows and 151 columns (presolve time = 63s) ...
Presolve removed 4808025 rows and 179 columns (presolve time = 68s) ...
Presolve removed 4808025 rows and 179 columns (presolve time = 70s) ...
Presolve removed 4808489 rows and 179 columns (presolve time = 77s) ...
Presolve removed 4809226 rows and 179 columns (presolve time = 80s) ...
Presolve removed 4809416 rows and 179 columns (presolve time = 85s) ...
Presolve removed 4809428 rows and 179 columns (presolve time = 90s) ...
Presolve removed 4809428 rows and 179 columns (presolve time = 95s) ...
Presolve removed 4809428 rows and 179 columns (presolve time = 103s) ...
Presolve removed 4809428 rows and 179 columns (presolve time = 108s) ...
Presolve removed 4809428 rows and 179 columns (presolve time = 110s) ...
Presolve removed 4809428 rows and 179 columns (presolve time = 115s) ...
Presolve removed 4883029 rows and 179 columns (presolve time = 125s) ...
Presolve removed 4883029 rows and 179 columns (presolve time = 130s) ...
Presolve removed 4883029 rows and 189 columns (presolve time = 138s) ...
Presolve removed 4883029 rows and 189 columns (presolve time = 141s) ...
Presolve removed 4883029 rows and 189 columns
Presolve time: 141.33s
Presolved: 1128106 rows, 692911 columns, 15981202 nonzeros
Variable types: 0 continuous, 692911 integer (692760 binary)
Deterministic concurrent LP optimizer: primal simplex, dual simplex, and barrier
Showing barrier log only...
Root barrier log...
Elapsed ordering time = 5s
Elapsed ordering time = 10s
Elapsed ordering time = 15s
Elapsed ordering time = 22s
Elapsed ordering time = 25s
Elapsed ordering time = 30s
Ordering time: 34.68s
Barrier performed 0 iterations in 195.31 seconds
Error termination0 -
-
-
Hi Martin,
This is most likely an out-of-memory error.
Could you try solving the model with Threads set to 1 and Method set to 0 or 1? If the solution process proceeds, then it is definitely an out-of-memory error. Note that by setting the 2 parameters, the solution time may increase drastically.
Our Knowledge Base article on How do I avoid an out-of-memory condition? might be of interest for you.Best regards,
Jaromił0 -
-
Hi Jaromił,
thanks for the quick reply! Both suggested parameter adjustments prevent the error so this seems to be memory related.
Thanks again for you help, best regards
Martin
0 -
投稿コメントは受け付けていません。
コメント
5件のコメント