Paul Hauner d34f922c1d Add early check for RPC block relevancy (#2289) ... ## Issue Addressed NA ## Proposed Changes When observing `jemallocator` heap profiles and Grafana, it became clear that Lighthouse is spending significant RAM/CPU on processing blocks from the RPC. On investigation, it seems that we are loading the parent of the block *before* we check to see if the block is already known. This is a big waste of resources. This PR adds an additional `check_block_relevancy` call as the first thing we do when we try to process a `SignedBeaconBlock` via the RPC (or other similar methods). Ultimately, `check_block_relevancy` will be called again later in the block processing flow. It's a very light function and I don't think trying to optimize it out is worth the risk of a bad block slipping through. Also adds a `New RPC block received` info log when we process a new RPC block. This seems like interesting and infrequent info. ## Additional Info NA		2021-06-02 01:07:27 +00:00
..
src	Add early check for RPC block relevancy (#2289)	2021-06-02 01:07:27 +00:00
Cargo.toml	Network protocol upgrades (#2345)	2021-05-28 22:02:10 +00:00