#13991: Mitigate speed regressions in symmetric function related code due to
#12313
---------------------------------+------------------------------------------
Reporter: nbruin | Owner: sage-combinat
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.8
Component: combinatorics | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: #13605 | Stopgaps:
---------------------------------+------------------------------------------
Comment (by nbruin):
It does change the order of memory usage in something like
{{{
P = partition_object
for k in [1..10^6]:
P.WeylGroup(k)
}}}
or whatever the syntax is. Is it clear that only a very limited range of
values for `k` is going to be used on the same object? Or that they are
obviously meant to remain in memory?
Every time you cache a parametrized result, you are creating a memory leak
for the lifetime of the object on which it's cached.
You'd hope that such a leak might be mitigated by occasionally deleting
the cached-on object, but in fact you can't control the lifetime: someone
else might be holding a reference, keeping the object alive. That's one
illustration of how "unique parents" are such a nasty hack. They ensure
that global state is essential for nearly any problem.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13991#comment:41>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
