My experience so far:
By running all 8 nodes with safe vault run-baby-fleming
my machine runs out of memory by nodes working on 100% processor load after couple minutes (not measured). Interestingly, nodes 7 & 8 do not take part in this – they are tiny processes with 0% load all the time.
When I figured out how to run less nodes, things got better. With 1, 2 and 3 nodes all was fast and snappy. No constant load on processor and CLI commands responded quickly.
With 4th node joining the party, things started to get messy. It took couple minutes for processor load to settle down (not measured, by about 2-5 min.), during this time CLI commands had some lag. Last node to stop eating my processor was newly joined node, the 4th one.
5th one spoiled everything. Until now (about 1h after joining) processor load is 100%, although nodes 1 & 2 are not eating my memory, unlike 3, 4 & 5, which currently eat 20% memory each and counting. 1 & 2 oscillate around 1% mem each, but are higher on CPU (~60% each, while 3, 4 & 5 ~23%). I’m not sure if it’s like that from the beginning, or was it different just after #5 joined. CLI commands lag heavily, even simple, like safe keys balance
, and sometimes I get errors. Just like with default 8 nodes.
After running more safe keys balance
commands, vaults 1 & 2 started to grow.
Next step was to try to kill vaults from the youngest ones. After killing 5, 4 & 3 in ~5min intervals, nodes 1 & 2 still use all the processor and grow in memory usage, so I’m going to kill them as well. safe keys balance
stopped to get errors (“Connection timed out when bootstrapping to the network”) and return balance after ~10s.
After killing vault #2, genesis vault memory usage dropped from 15% to 3% and CPU also from 100% to ~70%. Commands run fast (~1s), although not as fast as with fresh 3 nodes. Time to kill it too!
BTW my system is little outdated: 1.8 Core 2 Duo, 4G mem, SSD drive, Arch Linux.