Removed peer authenticated assert in Floodgate::broadcast #4680
+1
−11
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.
Description
Resolves https://github.com/stellar/stellar-core-internal/issues/335
This PR removes an expensive assert in
Floodgate::broadcast
. This assert had to acquiremStateMutex
from the main thread, but would often be blocked by the background thread. During periods of high load (1850 TPS), waiting for this mutex would double the median time of broadcast. Because a peer's authenticated state can only be changed from the mainthread anyway, the assert was replaced with a lockless main thread assert. During testing at 1850 TPS, this change resulted in a 15% decrease of txset fetch time, as well as a 10% decrease in nomination latency.Checklist
clang-format
v8.0.0 (viamake format
or the Visual Studio extension)