#12313: Fix yet another memory leak caused by caching of coercion data
--------------------------------------------------+-------------------------
       Reporter:  SimonKing                       |         Owner:              
                             
           Type:  defect                          |        Status:  
needs_review                             
       Priority:  major                           |     Milestone:  sage-5.3    
                             
      Component:  memleak                         |    Resolution:              
                             
       Keywords:  coercion weak dictionary        |   Work issues:              
                             
Report Upstream:  N/A                             |     Reviewers:  Simon King, 
Jean-Pierre Flori, John Perry
        Authors:  Simon King, Jean-Pierre Flori   |     Merged in:              
                             
   Dependencies:  #11521, #11599, #12969, #12215  |      Stopgaps:              
                             
--------------------------------------------------+-------------------------

Comment (by nbruin):

 Replying to [comment:172 jpflori]:
 > Running make ptest on a quite recent computer (12 threads), makes the
 runtime go from about 399 seconds on vanilla 5.3.beta2 to about 407
 seconds on 5.3.beta2 + #715 + #11521 + #12313 averaging on a few runs.
 >
 > On sage/schemes/elliptic_curves/sha_tate.py alone with long tests it
 goes from about 79 secs to about 82.5 secs.

 Well, cacheing does have a benefit. If you have enough memory, it's
 sometimes faster to simply not do any deallocation or garbage collection.
 It's nice if we can do this without performance loss but I think not
 leaking memory is worth some speed. Speed in exchange for a leak often
 means that you'll be able to run out of memory faster.

 I guess the key is getting confident that the time is lost in recomputing
 things that have been rightfully collected rather than computations
 performing slower. People can solve the first by keeping references to
 things they know they'll need again.

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