[Shiden] OOM issue during sync stage (archive node)

[w4llisz]

While running a Shiden node (archive mode) during the sync phase, the process was repeatedly killed due to OOM (Out of Memory).

Additional Information
• Network: Shiden
• Node mode: Archive
• Disk: 1.5 TB (/data)
• RAM: 64 GiB
• CPU: 8
• OS: Ubuntu 20.04

start command

docker run -d \
  --name shiden-container \
  --restart unless-stopped \
  -p 30333:30333 \
  -p 9933:9933 \
  -p 9944:9944 \
  -p 9615:9615 \
  -v /data:/data \
  staketechnologies/astar-collator:latest \
  astar-collator \
  --pruning archive \
  --rpc-cors all \
  --name shiden-node \
  --chain shiden \
  --base-path /data \
  --prometheus-external \
  --prometheus-port 9615 \
  --rpc-external \
  --rpc-methods Unsafe \
  --rpc-port 9933 \
  --enable-evm-rpc \
  --telemetry-url 'wss://telemetry.polkadot.io/submit/ 0'

[w4llisz]

Attached memory usage graph shows the growth pattern:

[w4llisz]

After upgrading to 128GB of memory, it worked normally. I’d like to know how to make it run properly on a machine with 64GB of memory.

[kamilsa]

@w4llisz Can you please check on this branch?
https://github.com/turuslan/astar/tree/state-sync-resume

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.