computeScore performance issue

[twoeths]

Motivation

• We keep computing peer score in a lot of places without any cache
• It's not scalable: the more messages, the more function calls we have for computeScore()(). When there are a lot of messages, it takes 4% cpu time of lodestar
  1130_lodestar_subscribeAllSubnets_local.cpuprofile.zip

Note

• It's not likely it's a performance issue of computeScore() function itself

[dapplion]

@tuyennhv I had the same though on this, we compute the scores incredibly often. You could add some quick and dirty metrics to know how many times computeScore() is called per second