-
Notifications
You must be signed in to change notification settings - Fork 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
Concurrency where possible #9
Comments
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
By design the main algorithm is sequential. But there are other places we can look to improve by work sharing. Mostly in the
utils
module, where we iterate over all triangle faces.I took a quick look at throwing rayon
par_iter
s where ouriter
s exist, but that blew up the time on my machine. I have 28 work threads, so I don't know if that's just rayon not allocating correctly and I had too much setup overhead, or that the iterators are just poorly implemented for parallelism. In any case, further investigation than a 5 minute plug and play is required.The text was updated successfully, but these errors were encountered: