perf(core): remove newly added body validation until we know its needed outside of syncing#2970
Conversation
…ain it during syncing
Lines of code reportTotal lines added: Detailed view |
|
Running the benchmark showed a 10% improved performance after removing the function call from I'm going to create an issue for checking possible missing validations and also to take a look at how #2658 affected syncing performance. |
fmoletta
left a comment
There was a problem hiding this comment.
Shouldn't we add validate_block_body to where validate_block is used in syncing?
As far as I can tell, the validate block body added here was just an addition, we are already checking bodies on request here: ethrex/crates/networking/p2p/peer_handler.rs Line 248 in ff28c6c Or am I missing something? |
|
Issue #2977 created |
My bad, I thought it was added because we were using |
…ed outside of syncing (lambdaclass#2970) **Motivation** This removes an additional validation done on the pre-execution of blocks as part of [this PR](lambdaclass#2658) **Description** Remove the call to the `validate_block_body` in `validate_block` Closes lambdaclass#2973
Motivation
This removes an additional validation done on the pre-execution of blocks as part of this PR
Description
Remove the call to the
validate_block_bodyinvalidate_blockCloses #2973