-
Notifications
You must be signed in to change notification settings - Fork 56
Multi-core Processing #7
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
Comments
For what I know Numpy is already using multithreading, so I cannot think it can be made faster using multiprocessing. Anyways I made a quick edit of the raytracer to check that splitting pixels in the cores. It runs slower:
|
Ah good to know. I suspected it would run slower but I wasn't sure and I don't have the chops to write it up well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just came across this article and started to wonder if it is also another option to speed up the raytracing in Python.
https://medium.com/@urban_institute/using-multiprocessing-to-make-python-code-faster-23ea5ef996ba
There is a cost so without experimenting I'm not sure if it will be more efficient yet but I believe that by default Python is single core (I could be wrong).
However it could find out how many cores you have and send out chunks of pixels to be calculated on different cores and return them. You can find out how many cores with:
Could be interesting to play with to see if it can get even faster. :)
The text was updated successfully, but these errors were encountered: