Use Latest state provider if possible in block_state_provider

[Rjected]

Currently block_state_provider does the following, constructing a historical state provider based on the anchor hash:

reth/crates/storage/provider/src/providers/blockchain_provider.rs

Line 141 in c1918d2

fn block_state_provider(

This means, that if there is an overlap of in-memory blocks and the DB, even if we could use the latest state provider for state, a historical state provider may be constructed.

This leads to some redundant I/O, a 25-35% hit on all storage reads whenever we've constructed a historical state provider. Specifically this is redundant history_info calls, that always hit the InPlainState | MaybeInPlainState branch.

We could instead:

• open a DB TX
• determine if the BlockState is a direct extension of the DB state
• If so, use the latest state provider

[nadtech-hub]

I would like to make it

[Rjected]

I would like to make it

@nadtech-hub please let me know how you plan on approaching this problem, and feel free to submit a PR!

[nadtech-hub]

@Rjected
I am reviewing code and making up the plan