reduce spike between get_payload and new_payload #7
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.
As TPS increases, the time-consuming spikes of
interval3_between_get_payload_and_new_payload
in the sequence logic will increase. As shown in the following figure:After debugging, it was found that the
try-update-engine
in the derived logic was executed before thenew_payload
function handler was executed.The purpose is to reduce the number of
try-update-engine
calls. Thetry-update-engine
event is triggered in four places, and the effects of the triggering are the same. Each block generation will trigger thetry-update-engine
event, so directly deletingtry-update-engine
in the derived logic will not have any effect.The same TPS spikes after modification are as follows: