About MemLimit

Answered

Charitha Buddhika Heendeniya

November 03, 2022 07:28

• 
• 
• 

Dear all,

I'm trying to use MemLimit parameter 

e = Env("gurobi.log", params={'MemLimit': 31,
                              'PreSparsify': 1,
                              'MIPFocus': 3,
                              'NodefileStart': 0.5,
                              'Heuristics': 0.3,
                              'Presolve': 1})

But when I do that, the OutOfMemory error is raised well before the 31GB RAM use. In fact the operation crashes at about 20GB memory use (checked via task manager). Do you know why this might happen?

0

• Official comment

  

  Simranjit Kaur

  • Gurobi Staff

  November 16, 2025 23:25

  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 try Gurobot, our chatbot interface offering instant, expert-level support.
• 

  Charitha Buddhika Heendeniya

  November 03, 2022 08:13

  • 
  • 
  • 

  Adding one more observation: OutofMemory is observed right at the end of the presolve. 

  0
• 

  Matthias Miltenberger

  • Gurobi Staff

  November 03, 2022 10:58

  Hi Charitha,

  it may happen that Gurobi requests more memory but doesn't use it, yet. The idea of the MemLimit parameter is mainly to allow a more controlled termination without actually using too much memory and disturbing other processes.

  Did you try running without setting the MemLimit parameter?

  Cheers,
  Matthias

  0
• 

  Charitha Buddhika Heendeniya

  January 12, 2023 15:55

  • 
  • 
  • 

  Sorry for the late reply. I did experiment with and without it. Without the MemLimit parameter, the OS takes care of the problem, but that occurs later. So probably, the behavior of Gurobi MemLimit is, as you said, related to some anticipated future memory use. 

  0

Post is closed for comments.