You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering why tests seem to execute so sequentially. I think I figured it out: each of our N threads runs while let Some(path) = todo.pop() {; that means if the queue is ever empty when they look at it, the thread terminates and does not come back!
I think we might want to use rayon with its thread pool, rather than trying an ad-hoc implementation of a threadpool ourselves.
The text was updated successfully, but these errors were encountered:
I was wondering why tests seem to execute so sequentially. I think I figured it out: each of our N threads runs
while let Some(path) = todo.pop() {
; that means if the queue is ever empty when they look at it, the thread terminates and does not come back!I think we might want to use rayon with its thread pool, rather than trying an ad-hoc implementation of a threadpool ourselves.
The text was updated successfully, but these errors were encountered: