We've been working on making HUGE family trees more accessible (we were having performance issues with graphs above 800 profiles big). I did a pairing session with @ahdinosaur looking into possible bottle necks.

In the meantime @Maui (Android) (Ben) found some really nice optimisations that stopped vuex (like redux) getters getting hammered 600k times. Impressive debugging.

@cherese built an awesome search feature which helps you find a node and open a path down to it, while collapsing other parts of the graph. trivial in the above case, gets pretty invaluable when you have 5k people in a family tree!

Here's an example of a graph with 1300 people in it. We don't need to see them all the explore whakapapa / context