# Memory consumption growth with many large MILP's in JuMP

**URL:** https://discourse.julialang.org/t/memory-consumption-growth-with-many-large-milps-in-jump/61895
**Category:** Optimization (Mathematical)
**Tags:** jump, optimization
**Created:** [May 27, 2021, 12:29am UTC](https://discourse.julialang.org/t/memory-consumption-growth-with-many-large-milps-in-jump/61895 "2021-05-27T00:29:27Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![nlaws](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nlaws/32/22205_2.png) [@nlaws](https://discourse.julialang.org/u/nlaws)
#### Post date: [May 27, 2021, 9:50pm UTC](https://discourse.julialang.org/t/memory-consumption-growth-with-many-large-milps-in-jump/61895/7 "2021-05-27T21:50:32Z")

</div>

Here are the `GC` results, i.e. I ran:

```julia
using REoptLite, JuMP, Xpress

for _ in range(1,stop=500)
    m = Model(Xpress.Optimizer)
    r = run_reopt(m, "outage.json")
    GC.gc()
end

```

 ![xpress_with_GC](https://global.discourse-cdn.com/julialang/original/3X/9/2/92b04e1c928c95c41ecfb5fc942251ee0343f09f.png)  
(Note that I ran 1,000 scenarios without `GC`).

Interesting that the memory usage still grows, but not as fast as without `GC`. Does that tell us anything?

---

_[View the full topic](https://discourse.julialang.org/t/memory-consumption-growth-with-many-large-milps-in-jump/61895)._