Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix of block proc metrics #290

Closed

Conversation

rus-alex
Copy link
Contributor

More accurate measurements of blocks processing metrics.

@rus-alex rus-alex requested a review from andrecronje as a code owner April 25, 2022 14:12
@@ -311,11 +310,25 @@ func consensusCallbackBeginBlockFn(

_ = evmProcessor.Execute(txs, false)

startOfBlockWriting := time.Now()

evmBlock, skippedTxs, allReceipts := evmProcessor.Finalize()
Copy link
Contributor

@thaarok thaarok Apr 28, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rus-alex There is an overlap between the blockExecutionTimer and blockWriterTimer intervals, which complicates using them for the Opera profiling, as evmProcessor.Finalize() is included in both of them.

As evmProcessor.Finalize() includes mostly statedb.Commit and trieproc time is measured for the blockWriterTimer too, I suggest to include it only into the blockWriterTimer interval - move the blockExecutionTimer end before the startOfBlockWriting.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@rus-alex
Copy link
Contributor Author

rus-alex commented Sep 6, 2022

Outdated, see #358 and #363

@rus-alex rus-alex closed this Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants