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
Currently every fork/join in the implicitly generated DAG has a latch that blocks until all the "fork subtasks" are executed. This is not optimal thread pool usage as blocking is not required here and introduces unnecessary overhead.
An asynchronous execution model should be used instead, with a single latch that wraps everything in order to synchronize it with the "rest of the world".
Currently every fork/join in the implicitly generated DAG has a
latch
that blocks until all the "fork subtasks" are executed. This is not optimal thread pool usage as blocking is not required here and introduces unnecessary overhead.An asynchronous execution model should be used instead, with a single
latch
that wraps everything in order to synchronize it with the "rest of the world".Pseudocode example:
The text was updated successfully, but these errors were encountered: