Set fullsweep_after=0 on the writer process #166
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This seems to increase throughput by ~10% on OTP26 and even more on OTP27. In particular, it seems to solve the performance regression with small messages on OTP 27: stream-perf-test -s 100 results (single node, everything local): OTP26 as-is: 880k OTP26, fullsweep_after 0: 940k OTP27 as-is: 750k OTP27 fullsweep_after 0: 1M
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 seems to increase throughput by ~10% on OTP26 and even more on OTP27. In particular, it seems to solve the performance regression with small messages on OTP 27:
stream-perf-test -s 100 results (single node, everything local): OTP26 as-is: 880k
OTP26, fullsweep_after 0: 940k
OTP27 as-is: 750k
OTP27 fullsweep_after 0: 1M