#12004: copying a linear program using Coin solver consumes enormous amounts of
memory
----------------------------------+-----------------------------------------
Reporter: john_perry | Owner: ncohen
Type: defect | Status: new
Priority: major | Milestone: sage-4.8
Component: linear programming | Keywords: linear programming, Coin,
copy, memory
Work_issues: | Upstream: N/A
Reviewer: | Author: john_perry
Merged: | Dependencies:
----------------------------------+-----------------------------------------
Comment(by john_perry):
FWIW, I'm fairly convinced that initializing with the GLPK backend is not
the problem. I tried the following modifications:
* change `__init__` in MixedIntegerLinearProgram so that `solver==None`
actually gives ''no'' backend, not the GLPK backend;
* in `__copy__`, initialize with `solver==None`.
I know it is a bad, bad idea to change the behavior of an initializer this
way, but I thought it would give unequivocal evidence. I've changed my
version back.
Indeed, '''even in this case''', copying a Coin solver consumes enormous
memory. It seems easier to break out of the loop, though. In fact, within
15 loops it consumes 1.6GB RAM. That's not a typo: only 15!!! `8-0`
So the problem really does lie elsewhere.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12004#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
