We’re steaming ahead with some scalability improvements so that we can know that Elemental Chat for Hosts will be ready to work on at least 500 HoloPorts.
Last week we shared a list of the activities we were exploring to address the latency build up after the app has been deployed and run on many nodes for several weeks. We’ve completed several of the improvements and are midway into a few others:
- We’ve limited large chat messages from being sent in the app
- We’ve tested the proxy server infrastructure fully and we identified improvements at the Holochain layer
- Specifically, we’ve reduced the volume of network traffic in Holochain limiting republishing of data (temporary measure until we implement validation receipts to measure publishing success).
- We’ve abstracted Holochain networking config into settings that the Holo team can modify to tweak early stage optimisations for gossip traffic
- We are finalising some change in the HoloPort OS configuration that will allow us to disable older versions of the app which are still running in the background and taking up bandwidth of the proxy server
- We’re updating the TryCP test framework so that we can run tests at scale for RSM applications
- We’re fixing a bug in Elemental chat that has users experience instant signal messages dropping when gossip updates into the UI
While a small group of our developers are working on all the things that will let us release Elemental Chat to hosts, many others are also making great progress on the apps and features that will get us to Beta. The Holo team is still on track this month to get the hosted version of Elemental chat into test. We’ve begun UI development on the Host Console and the HoloFuel DNA has been updated to work on Holochain RSM. We’ve also completed work on our Holo app registration process and KYC.
Things are really coming together. We should have a short update at the end of the week and we’ll be able to see the results of the automated testing by next week.