#715: Parents probably not reclaimed due to too much caching
------------------------+---------------------------------------------------
   Reporter:  robertwb  |          Owner:  somebody           
       Type:  defect    |         Status:  needs_review       
   Priority:  major     |      Milestone:  sage-4.8           
  Component:  coercion  |       Keywords:  weak cache coercion
Work_issues:            |       Upstream:  N/A                
   Reviewer:            |         Author:  Simon King         
     Merged:            |   Dependencies:  #9138, #11900      
------------------------+---------------------------------------------------

Comment(by SimonKing):

 Replying to [comment:102 jpflori]:
 > Testing sage.schemes with only one core gave me:
 >
 >  * 1526.0 sec on vanilla
 >
 >
 >  * 1538.8 sec on vanilla +
 [http://trac.sagemath.org/sage_trac/search/opensearch?q=ticket%3A715 #715]

 That's very good news indeed!

 > Running five tests of sage.schemes.elliptic_curves.padic_lseries gave
 me:
 >
 >  * 51.0, 48.7, 47.0, 47.0, 47.1 on vanilla
 >
 >
 >  * 49.0, 47.2, 48.4, 47.4, 47.7 on vanilla +
 [http://trac.sagemath.org/sage_trac/search/opensearch?q=ticket%3A715 #715]

 That looks like quite some randomness.

 > My next step is to check for the memory leaks (same j invariant,
 different j invariants, finite field example of Paul in
 [http://trac.sagemath.org/sage_trac/search/opensearch?q=ticket%3A11521
 #11521] ? or do that last one need a patch for the
 [http://trac.sagemath.org/sage_trac/search/opensearch?q=wiki%3AHomSet
 HomSet] cache ?

 Yes, the finite field example is not solved:
 {{{
 sage: for p in prime_range(10^5):
 ....:     K = GF(p)
 ....:     a = K(0)
 ....:
 sage: import gc
 sage: gc.collect()
 0
 }}}

 So, I am going to modify the ticket description of #11521, indicating that
 the original elliptic curve example has been tackled here, but that there
 remains an orthogonal problem.

 > Afterward, I'll properly review your code and examples (that I've
 already seen many times obviously :)).

 Not so many times: Some examples are only in the very latest version of
 the second patch.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:103>
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.

Reply via email to