New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Huge speed regression in some tests after matplotlib upgrade #24862
Comments
comment:1
Yes, several others with |
comment:2
The easiest speed up is to replace |
comment:3
These are the slow tests from running
|
comment:4
OK. Replying to @jdemeyer:
Probably not the upgrade, just tachyon being slow.
That warrants examination in whatever case. 4s in 2011 to 49s in 2018 with probably newer hardware.
Uncertain.
Those two are prime suspect as they both use
Nothing involving MPL directly, this is probably something else. That's certainly a long test. How old is your hardware that's what I get locally
|
comment:5
This is my POWER 8 ppc64le machine. So not old, but perhaps unusual. |
comment:6
That explains things. POWER chips are notoriously bad at interpreted languages, my power7 boxes would be giving similar results. |
comment:7
Tests 1, 2 and 6 in that list are also slow on Sage 8.1. So they are not caused by matplotlib. |
comment:8
Regardless of hardware, it's still a regression of a factor 300. |
This comment has been minimized.
This comment has been minimized.
comment:10
Do you happen to know how doctests "plot" stuff? I am asking because I'm trying to reproduce the problem outside the doctesting framework but I don't know how. |
comment:11
Duplicate of #13135 |
comment:12
For normal plots you can iterate over the elements, which is usually a reasonably detailed textual representation
There is no similar solution for 3d plots afair. Reducing the output resolution of tachyon would be fine with me; we don't test anything by raytracing big images instead of small ones except possibly for our patience. |
On this machine
this test now takes 926 seconds
Before the matplotlib upgrade at #23696, this took about 3 seconds.
CC: @kiwifb @vbraun
Component: graphics
Issue created by migration from https://trac.sagemath.org/ticket/24862
The text was updated successfully, but these errors were encountered: