#11900: Serious regression caused by #9138
---------------------------+------------------------------------------------
Reporter: SimonKing | Owner: tbd
Type: defect | Status: needs_work
Priority: blocker | Milestone: sage-4.7.2
Component: performance | Keywords: categories regression
Work_issues: | Upstream: N/A
Reviewer: | Author: Simon King
Merged: | Dependencies: #9138
---------------------------+------------------------------------------------
Comment(by SimonKing):
I have attached a second patch, in which I implemented the ideas sketched
above. Doc tests need work (I guess some old tests will need to be
rewritten).
There is some improvement in the timings, With sage-4.7.2.alpha3 and both
patches applied, I get:
{{{
sage: %time L = EllipticCurve('960d1').prove_BSD()
CPU times: user 5.01 s, sys: 0.06 s, total: 5.07 s
Wall time: 5.22 s
}}}
Sage-4.7.2.alpha2 took 4.01 s on that example. Thus, with the second
patch, we "only" have half of the regression that we had after the first
patch, and only one fifth of the regression without both patches.
The other critical example became:
{{{
sage: E = EllipticCurve('389a')
sage: %time test(E)
CPU times: user 15.93 s, sys: 0.04 s, total: 15.97 s
Wall time: 16.03 s
}}}
Sage-4.7.2.alpha2 took 16.73 s. Hence, here we actually have a slight
improvement, where we previously had a drastic regression.
I need more tests, but I think that I can now hope to "rescue" #9138.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11900#comment:27>
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.
