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
My peers and I looked through the code and noticed that the .get() was placed immediately after the async. This likely means that there is only one thread that is doing useful work despite there being many threads made (all the other threads are blocking on the .get().
This may be an issue because this implementation is not fully using threads to its advantage.
-- Try looking at the CPU utilization when running HermesBDD on a large test case
(I found 10x10 nqueens as a nice balance between being large and actually finishing in a sane amount of time)
When you do so, the CPU utilization for me is around ~102%, when it should be n00% where n is the number of cores I have available.
If further technical details might be helpful for you all, please let us know!
My peers and I looked through the code and noticed that the .get() was placed immediately after the async. This likely means that there is only one thread that is doing useful work despite there being many threads made (all the other threads are blocking on the .get().
This may be an issue because this implementation is not fully using threads to its advantage.
HermesBDD/src/node.cpp
Line 346 in 0336f03
The text was updated successfully, but these errors were encountered: