On Tue, 17 Apr 2012 at 11:32AM +0200, Jeroen Demeyer wrote:
> Now that we're (hopefully) nearing the sage-5.0 release, I am doing
> some timings again. We don't yet have proper automatic timing testing,
> but with some simple scripting I discovered that plotting has severely
> slowed down. I haven'
This is now http://trac.sagemath.org/sage_trac/ticket/12854
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-de
On Tuesday, April 17, 2012 5:52:42 PM UTC+8, Jeroen Demeyer wrote:
>
> An easy way to test this using timeit() (best out of 20 runs):
>
> sage:
>
> timeit('''plot(sin(x),(x,0,2*pi),ticks=pi/3,tick_formatter=pi).save("/tmp/1.png")''',
> number=1, repeat=20)
>
Maybe the slowdown is not in matplotl
An easy way to test this using timeit() (best out of 20 runs):
sage:
timeit('''plot(sin(x),(x,0,2*pi),ticks=pi/3,tick_formatter=pi).save("/tmp/1.png")''',
number=1, repeat=20)
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Now that we're (hopefully) nearing the sage-5.0 release, I am doing some
timings again. We don't yet have proper automatic timing testing, but
with some simple scripting I discovered that plotting has severely
slowed down. I haven't figured out precisely why.
For example the following command (i
