Target performance for use in peerpad about peer-crdt HOT 1 CLOSED

For the DAG operations test, I had three peers in the network, where each peer was chosen randomly to apply one of N operations to a lww-register CRDT. This was a stress test, where all of the operations were performed rapidly, to see how long it would then take for the peers to converge.

When N was 500, it took the three peers 17 minutes to converge.

When N was 1000, the test ran for over 5 hours and then crashed from lack of RAM.

Profiling showed a performance bottleneck in the _isChildOf() log method, and an improved version of the method has been patched in #8

Using the patched version, 500 changes took ~30 seconds before convergence, and 1000 changes took 70-80 seconds.

This is remarkably faster than before, but likely needs more optimization since this was using the virtual network used by the current tests and not including real-world network latency costs.

from peer-crdt.