problem with optimization memory exhausted

[Vivi]

Dear Robert,

I have had the following statement in my model running log:

"Optimization exhausted available memory

Waiting for other threads to finish...       83991s
Waiting for other threads to finish...       84121s
Waiting for other threads to finish...       84250s
Waiting for other threads to finish...       84379s

Waiting for other threads to finish...       84507s
Warning: Possible non-determinism after error

Explored 0 nodes (0 simplex iterations) in 84607.49 seconds (173791.74 work units)
Thread count was 1 (of 12 available processors)

Solution count 0

Solve interrupted (error code 10001)
Best objective -, best bound -, gap -
Gurobi 10.0.3: ran out of memory
ampl: "

I interrupted AMPL after a day period (24h=84600s) of running.

I would like to ask you if I continued to run the model after 24 hours, could AMPL have given a solution to the model, given the elements that are in the log. And what do you think I must do have AMPL give solution to that problem.

Many thanks for your help.

Best regards.

[AMPL Google Group]

The main part of Gurobi's algorithm builds a search tree. Even in a successful run, the search tree can grow quite large during the solver run. Error code 10001 indicates that the search tree became too large to fit in your computer's RAM memory. To avoid this error, you can use Gurobi's nodefilestart setting to limit the amount of memory used for search nodes; when the number of gigabytes of memory exceeds the the nodefilestart value, nodes are compressed and written to disk. Gurobi recommends trying 0.5, which can be specified by adding nodefilestart=0.5 to your gurobi_options string -- or if you are not yet specifying a gurobi_options string, by giving the command

option gurobi_options 'nodefilestart=0.5';

before solving. You can experiment with larger nodefilestart values if your computer has a large amount of memory, but keep in mind that Gurobi will also need a substantial amount of memory for other purposes besides building the search tree.

Also you can add a timelim setting to your gurobi_options string, to stop the solver run normally rather than interrupting it. For example, timelim=86400 will stop the run after 1 day. Information on all Gurobi settings can be found on our Gurobi Options page.

Finally, if you need to ask for more help, ask Gurobi for a detailed log by adding outlev=1 to your gurobi_options string. Then include all of the resulting log listing with your question; since the log may be very long, you may want to copy it to a file, then attach the file.

--
Robert Fourer

We're switching to a new, enhanced user forum.
Join it now at discuss.ampl.com.

{#HS:2398920890-120174#}

[Viviane]

Dear Robert,

Many thanks for your assistance.

I had put the gurobi_options string  outlev=1. Please find attached the entire log to see if there is additional information which can permit you to help more.

Also I would like to ask you for the larger nodefilestart values up to what values can I take.

Regards.

--
You received this message because you are subscribed to a topic in the Google Groups "AMPL Modeling Language" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ampl/JSZ_q0aymzg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ampl+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ampl/reply-77152-2398920890-7187225543-1698173571-397995261%40helpscout.net.

[AMPL Google Group]

This has been answered at discuss.ampl.com:
https://discuss.ampl.com/t/help-about-error-code-10001/781/2?u=4er
https://discuss.ampl.com/t/problem-with-error-code-10001-and-optimization-memory-exhausted/782/2?u=4er

--
Robert Fourer

We're switching to a new, enhanced user forum.
Join it now at discuss.ampl.com.

{#HS:2398920890-120174#}

On Wed, Oct 25, 2023 at 12:09 PM UTC, AMPL Modeling Language <am...@googlegroups.com> wrote:

Dear Robert,

Many thanks for your assistance.
I had put the gurobi_options string outlev=1. Please find attached the entire log to see if there is additional information which can permit you to help more.
Also I would like to ask you for the larger nodefilestart values up to what values can I take.
Regards.

Le mar. 24 oct. 2023 à 14:52, AMPL Google Group <am...@googlegroups.com> a écrit :

On Tue, Oct 24, 2023 at 6:52 PM UTC, AMPL Google Group <am...@googlegroups.com> wrote:

The main part of Gurobi's algorithm builds a search tree. Even in a successful run, the search tree can grow quite large during the solver run. Error code 10001 indicates that the search tree became too large to fit in your computer's RAM memory. To avoid this error, you can use Gurobi's nodefilestart setting to limit the amount of memory used for search nodes; when the number of gigabytes of memory exceeds the the nodefilestart value, nodes are compressed and written to disk. Gurobi recommends trying 0.5, which can be specified by adding nodefilestart=0.5 to your gurobi_options string -- or if you are not yet specifying a gurobi_options string, by giving the command

option gurobi_options 'nodefilestart=0.5';

before solving. You can experiment with larger nodefilestart values if your computer has a large amount of memory, but keep in mind that Gurobi will also need a substantial amount of memory for other purposes besides building the search tree.

Also you can add a timelim setting to your gurobi_options string, to stop the solver run normally rather than interrupting it. For example, timelim=86400 will stop the run after 1 day. Information on all Gurobi settings can be found on our Gurobi Options page.

Finally, if you need to ask for more help, ask Gurobi for a detailed log by adding outlev=1 to your gurobi_options string. Then include all of the resulting log listing with your question; since the log may be very long, you may want to copy it to a file, then attach the file.

--
Robert Fourer

We're switching to a new, enhanced user forum.
Join it now at discuss.ampl.com.