Taras Woronjanski
Taras Woronjanski
Running i3en.6xlarge on AWS, node gets out of sync too frequently.
> Let me describe our expirience how to get synced node w/o issues. Key point is: > > * Use _low-latency_ disks(or terabytes of RAM for cache), 1.5TB+. This is...
> @FeurJak how can I verify how much cache do I use? Not too sure how you can verify it, but I set the cache size on my command: ./build/bin/geth...
> @FeurJak Pick up any [8+cpu 32GB+ RAM] instance on [GCP](https://cloud.google.com/compute/docs/disks#localssds) or [AWS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html#instance-store-volumes) with ephemeral local NVME disks and place BSC datadir on local NVME. You may attach additional disks...
what's the hardware or server specs that your node is running on? I have somewhat similar issues but I'm subscribing to only pending Txns and doing a Debug_TraceCall on each...