Node performance issues #1318
Description
On testnet the reporter nodes was most recently down.
https://metrics.internal.testnet.concordium.com/d/UjMEpEznz/alerts-critical?orgId=1&viewPanel=6&from=1737445170378&to=1737452333360
This was caused by the CCDScan indexer putting too much pressure on the node (It should not using the load be able to but nevertheless it happened). The issue then lies in after we stopped the indexer, the memory never recovered. After a restart of the reporter node it did however, indicating that the node does not clean up after it self.