Update from MaidSafe HQ
We’ve made good progress in narrowing down the main cause of the OOM issue seen with v5 and are testing out fixes. We have realised that we are unnecessarily reserialising the whole msg for every dst update - this is causing a huge memory spike in the nodes. We are in the process of changing this. You may have also noticed several other message efficiency improvements over the previous few days - we’re working to improve node throughput so the memory in question is not held for as long, and to reduce the number of messages across the network as a whole, with a simplified routing layer filter being our target there. We must add that even once all this is in place we don’t believe we are finished with improvements in this area just yet, with various other improvements being debated amongst the team, but we hope these changes will result in more robust testnet iterations in the meantime.
With Anti Entropy we believe we’re just about there with what we think are the last couple of bug and test fixes being finalised.
Once the OOM and Anti Entropy fixes are in place we intend to do some intensive testing in house. If this goes well then we may be in with a chance of a testnet v6 later tomorrow (Thursday), but there’s a lot of variables there and it only takes one bug to set that back.
As always, we’ll do our best to keep you up to date.
Thanks everyone