Performance: Status Cache

[bw-solana]

Status cache is by far the biggest bottleneck right now if you ingest many txs regardless of CUs, because it's an early bottleneck

It's using a rwlock now. The short term fix is to use a concurrent hash table. Dashmap would work, but Alessandro has been benchmarking https://docs.rs/flurry/latest/flurry and it's much much faster.

However, the existing design doesn’t scale well to 1M TPS without pre-allocating a ton of memory.

• Faster status cache #3796

[4r33x]

I think it's worth to try scc or even lock-free papaya over dashmap\flurry

[alessandrod]

I've looked into both of those a while ago and they don't provide the consistency guarantees required for the status cache