#13057: introspection is slow and causes a significant memory leak
--------------------------------------------+-------------------------------
Reporter: bober | Owner: mvngu
Type: defect | Status: needs_review
Priority: critical | Milestone: sage-5.1
Component: documentation | Resolution:
Keywords: regression introspection | Work issues:
Report Upstream: N/A | Reviewers:
Authors: John Palmieri | Merged in:
Dependencies: | Stopgaps:
--------------------------------------------+-------------------------------
Comment (by hivert):
Replying to [comment:25 ppurka]:
> I can confirm that this patch works, and fixes all the issues raised
here. But I know nothing about sphinx, so I am not sure about setting it
to positive review.
I wan't to have a close look at this one (understanding why there is a
such a huge slowdown/memleak). It seems that the intersphinx database is
recreated at each run (which is very bad wrt speed, caching the result
should be doable) and not garbage collected (which is even worse). But I
can't manage to find the time to do it. I is clearly critical or blocker.
I'm soory, I didn't find the time to even apply the patch. Does it
deactivate intersphinx when using {{{??}}} *in the notebook* ? If so, I
think we should look for a better solution because not calling
{{{find_sage_dangling_links}}} breaks hundreds of links (see #9128).
Sorry that my machine is very fast and that I didn't notice the problem
when writing #9128.
Cheers,
Florent
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13057#comment:26>
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.
