Use a cond var to sleep finalizer thread #179
Merged
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.
This commit first fixes an issue where Alloy did not record when a finalizer thread had already been spawned. This alone removes the finalizer count anomalies and brings performance back up to ~20% slower than our previous finalization model [1].
Second, by introducing a condition variable to sleep the finalizer thread when there is no work to do we now see that our elision benchmark results are statistically indistinguishable to [1].
[1]: Benchmarks run using Alloy from commit #abe23a2c