-
Notifications
You must be signed in to change notification settings - Fork 193
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
Performance hit with Honer's algorithm #2219
Comments
I can reproduce the issue. Investigating... |
Can you confirm that passing |
serge-sans-paille
added a commit
that referenced
this issue
Jul 13, 2024
… step This used to be enforced by distutils but it seems to no longer be the case. Fix #2219
It does work, now I have a 4.5x over pure Python, and a 6.5x on the real case. Thanks! |
serge-sans-paille
added a commit
that referenced
this issue
Jul 14, 2024
… step This used to be enforced by distutils but it seems to no longer be the case. Fix #2219
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider this code to evaluate polynomials (and make pretty fractals):
with
extern.py
:Running in pure Python mode, I get over 7 it/s, but with Pythran I get over 4 s/it. This is with both release and master, Python 3.11, on Fedora 40 (GCC 14.1.1).
I don't know what is going on, but this should be the kind of problems Pythran shines at.
Restricting ourselves to reals we get an even larger slow down, from 17 it/s in pure Python, down to 3.8 s/it with Pythran:
and
#pythran export newton_step(float64[:, :], float64[:], float64[:])
The text was updated successfully, but these errors were encountered: