Because requests with block information might be performed with the same information, pressure on the ES could be alleviated by introducing an intermediate caching layer
Proposed Changes
use getOrSetCache when fetching block info based on timestamp and shard id in deep history interceptor
How to test
Perform multiple requests with deep history information but for the same shardId and timestamp, and verify that the number of requests to ES stays linear
Reasoning
Proposed Changes
getOrSetCachewhen fetching block info based on timestamp and shard id in deep history interceptorHow to test