#715: Parents probably not reclaimed due to too much caching
------------------------+---------------------------------------------------
Reporter: robertwb | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: sage-4.8
Component: coercion | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
------------------------+---------------------------------------------------
Comment(by SimonKing):
I wonder whether the problem has already been solved. I just tested the
example from the ticket description, and get (at least with #11900, #11521
and #11115):
{{{
sage: K = GF(1<<55,'t')
sage: a = K.random_element()
sage: m0 = get_memory_usage()
sage: for i in range(1000):
....: E = EllipticCurve(j=a); P = E.random_point(); PP = 2*P
....:
sage: get_memory_usage() - m0
15.22265625
}}}
I think that this is not particularly scary. I'll repeat the test with
vanilla sage-4.8.alpha3, but this will take a while to rebuild.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:15>
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.
