-
Notifications
You must be signed in to change notification settings - Fork 22
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
Benchmarks #127
Comments
@olls but for pypy you don't want to use cProfile.. |
I'm not sure what you mean, I'm using the timeit module. |
Use environment variable |
@olls |
The cProfile part was already there. See my last comment to enable the timeit timings. |
@olls ah, ok |
On my machine I get around 0.05 seconds with python renderer, and 0.015 seconds with the C renderer. Which is promising, as there is a lot more space for optimisations in the C. |
@olls and where's resulting log will be located? |
The results are output to |
We'll document all this at some point... |
@olls I get render call time ~0.003 seconds So PyPy is actually not that slow compared to C |
But PyPy3 is not that well optimized as PyPy2 is |
So the 0.003 time was with PyPy? |
Yes |
So C is slightly faster |
I don't know much about PyPy, can you not run the C extension in it? |
@olls I can, but it will be slower than on CPython. You want to use CFFI on PyPy instead (it has some parts inside PyPy). |
OK, it might not be too much work to port our C renderer to CFFI then, we don't use much of the Python API, just to get the data in. |
@olls this is JIT log (you can even see PyPy generated JIT codes and ASM codes): |
OK, I'll have to look into PyPy some more. Thanks for your interest in the project :) |
@TiberiumPY
Things like render time and terrain generation speed.
The text was updated successfully, but these errors were encountered: