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
Being able to run tests multi-threaded simply by adding DIVAN_THREADS=XXX to get a feeling for contention is super nice.
However it seems like every benchmark run is using scoped threads under the hood.
Running a threaded benchmark through samply record, I end up with well beyond 6k "tracks", each of which is extremely short lived and it is pretty much impossible to select any of the background threads to do proper profiling.
It also appears that a large portion of the main thread time is actually spent creating / destroying threads themselves, at least on macOs where I tested this:
The text was updated successfully, but these errors were encountered:
Being able to run tests multi-threaded simply by adding
DIVAN_THREADS=XXX
to get a feeling for contention is super nice.However it seems like every benchmark run is using scoped threads under the hood.
Running a threaded benchmark through
samply record
, I end up with well beyond 6k "tracks", each of which is extremely short lived and it is pretty much impossible to select any of the background threads to do proper profiling.It also appears that a large portion of the main thread time is actually spent creating / destroying threads themselves, at least on macOs where I tested this:
The text was updated successfully, but these errors were encountered: