# Out-of-memory errors using Ipopt to solve very large-scale trajectory optimization problems

**URL:** <https://discourse.julialang.org/t/out-of-memory-errors-using-ipopt-to-solve-very-large-scale-trajectory-optimization-problems/98840>\
**Category:** Optimization (Mathematical)\
**Created:** [May 14, 2023, 4:24pm UTC](https://discourse.julialang.org/t/out-of-memory-errors-using-ipopt-to-solve-very-large-scale-trajectory-optimization-problems/98840 "2023-05-14T16:24:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![odow](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/odow/32/28685_2.png) [@odow](https://discourse.julialang.org/u/odow)\
**Post date:** [May 14, 2023, 7:09pm UTC](https://discourse.julialang.org/t/out-of-memory-errors-using-ipopt-to-solve-very-large-scale-trajectory-optimization-problems/98840/2 "2023-05-14T19:09:23Z")

</div>

Do you have a log of the solve? Does ipopt report the same number of nonzeros as you provide?

See also [Ipopt solves large-scale nonlinear problems - #3 by ccoffrin](https://discourse.julialang.org/t/ipopt-solves-large-scale-nonlinear-problems/98831/3)

---

_[View the full topic](https://discourse.julialang.org/t/out-of-memory-errors-using-ipopt-to-solve-very-large-scale-trajectory-optimization-problems/98840)._
