On Tuesday, January 27, 2015 at 10:05:02 AM UTC-8, vdelecroix wrote:
>
> Interesting. Note that the <string>:2 (<module>) part actually comes
> from hashing...
Why do you think that? According to the profiling, this gets called only
once, has a modest "total" time and a large variation in the "cumulative".
I think that line is just the scope of the routine directly called in the
profiling session (i.e., "top level"). The big difference that stands out
to me is:
1015588/1015586 9.816 0.000 33.706 0.000 homset.py:86(Hom)
versus
4/2 0.000 0.000 0.000 0.000 homset.py:83(Hom)
It suggests there is a homset that gets created and forgotten every time.
You should probably dig into the callgraph to see who is triggering this
call. It suggests to me that between 5.12 and 6.4, some memory leak in Hom
caching was resolved. In your particular case it suggests that you may now
have to do some extra work to keep the relevant homset alive (or some other
object that needs it).
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
