Profiling & Performance about cardano-node HOT 1 CLOSED

From @mrBliss

• The ChainSyncClient is currently not yet trimming candidate chains (PR in progress), so memory usage will inevitably grow when a node is connected to other nodes
  [11:27 AM]
• IntersectMBO/cardano-ledger#618
  [11:28 AM]
• We are planning to verify that the state of the node is in normal form, which would (theoretically) solve all space leaks
  [11:31 AM]
• Edsko is going to apply an optimisation to the LedgerDB that should address the cost centres at the top of my profiling output (with block validation disabled). (edited)
  [11:33 AM]
• The ChainSyncClient is not yet pipelined, which means that when we sync a bunch of blocks, they will be downloaded one-by-one with a relatively high fixed-cost per block (edited)

from cardano-node.