#12313: Fix yet another memory leak caused by caching of coercion data
--------------------------------------------------------+-------------------
       Reporter:  SimonKing                             |         Owner:        
                                               
           Type:  defect                                |        Status:  
needs_work                                           
       Priority:  major                                 |     Milestone:  
sage-5.7                                             
      Component:  memleak                               |    Resolution:        
                                               
       Keywords:  coercion weak dictionary              |   Work issues:  Speed 
regression                                     
Report Upstream:  N/A                                   |     Reviewers:  Simon 
King, Jean-Pierre Flori, John Perry, Nils Bruin
        Authors:  Simon King, Jean-Pierre Flori         |     Merged in:        
                                               
   Dependencies:  #715, #11521, #12215, #13746, #13378  |      Stopgaps:        
                                               
--------------------------------------------------------+-------------------
Changes (by SimonKing):

  * work_issues:  => Speed regression


Old description:

> The following could not be fixed in #715:
>
> {{{
> sage: K = GF(1<<55,'t')
> sage: for i in range(50):
> ....:     a = K.random_element()
> ....:     E = EllipticCurve(j=a)
> ....:     b = K.has_coerce_map_from(E)
> ....:
> sage: import gc
> sage: gc.collect()
> 0
> }}}
> The problem is that any parent has a dictionary that stores any coerce
> map (and a different dictionary for conversion maps) ending at this
> parent. The keys are given by the domains of the maps. So, in the example
> above, the field `K` has an attribute that is a dictionary whose keys are
> the different elliptic curves.
>
> In coercion, it is usually best to compare parents not by equality but by
> identity. Therefore, I suggest to implement a container called `MonoDict`
> that works similar to the new weak `TripleDict` (see #715), but takes a
> single item as a key.
>
> First tests show that one can actually gain a lot of speed: `MonoDict`
> can access its items much faster than a usual dictionary.
>
> __Apply__
>
>  * [attachment:trac_12313-mono_dict-combined-random-sk.patch]
>  * [attachment:trac_12313-safe_callback.patch]

New description:

 The following could not be fixed in #715:

 {{{
 sage: K = GF(1<<55,'t')
 sage: for i in range(50):
 ....:     a = K.random_element()
 ....:     E = EllipticCurve(j=a)
 ....:     b = K.has_coerce_map_from(E)
 ....:
 sage: import gc
 sage: gc.collect()
 0
 }}}
 The problem is that any parent has a dictionary that stores any coerce map
 (and a different dictionary for conversion maps) ending at this parent.
 The keys are given by the domains of the maps. So, in the example above,
 the field `K` has an attribute that is a dictionary whose keys are the
 different elliptic curves.

 In coercion, it is usually best to compare parents not by equality but by
 identity. Therefore, I suggest to implement a container called `MonoDict`
 that works similar to the new weak `TripleDict` (see #715), but takes a
 single item as a key.

 First tests show that one can actually gain a lot of speed: `MonoDict` can
 access its items much faster than a usual dictionary.

 __Apply__

  * [attachment:trac_12313-mono_dict-combined-random-sk.patch]

--

Comment:

 The patch is updated. I used the occasion to combine the two patches.
 Hence:

 Apply trac_12313-mono_dict-combined-random-sk.patch

 It still needs work, because of the speed regression.

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