Our monitoring history indicates the chain archiver occasionally exhibits memory spikes of up to approximately 30Gb, and very occasionally as high as 70Gb.
The snapshot size seems to be consistent between all sampled processes, so I imagine this memory spike relates to some unbounded operation the archiver is performing.
See the example of the memory profiles vs snapshots which illustrates the problem
Our monitoring history indicates the chain archiver occasionally exhibits memory spikes of up to approximately 30Gb, and very occasionally as high as 70Gb.
The snapshot size seems to be consistent between all sampled processes, so I imagine this memory spike relates to some unbounded operation the archiver is performing.
See the example of the memory profiles vs snapshots which illustrates the problem