Add optional argument to neglect domain_local_await
#4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, the benchmark framework replaces the blocking operations provided by
domain-local-await
, that useMutex
andCondition
by default, with a busy-wait based implementation. The reason for that is that suspending and later resuming a domain using a mutex and condition can be extremely expensive. The cost can be 100μs or 100kns on the "fermat" machine we currently use for benchmarking multicore code, for example, which is 2 to 3 orders of magnitude more than what typical lock-free operations take. So, when that happens in a benchmark, you are no longer measuring the lock-free algorithm and you are measuring the OS and OCaml runtime context switch cost. The result will then be basically just noise. Reconfiguring DLA allows to measure the cost it takes to support blocking rather than the cost of blocking itself.