It’s only going to progressively get better no doubt. Just bug fixes and performance improvements. Once the website is updated and a release candidate is pushed we’ll try to actually get more users. Between now and then there are a lot of little improvements to be made. For instance, doing some performance improvements on the log today. Right now is stores some data fairly inefficiently - namely log terms. Basically, the same term is usually repeated over and over for each entry, and terms always increase and never decrease in the log, so that makes it a good candidate for some improvements. Basically, the log should just log a term once and all subsequent entries should inheret that term. There’s also some opportunity to do less deserialization on servers. Right now everything is unnecessarily deserialized every time the log is accessed. For example, an entire entry is deserialized just to read the term. That’s unnecessary. There’s also some caching that can be done in the log to prevent writing an entry to disk and then reading it to send it to followers. It should also be modified to map only recent segments into memory when using
StorageLevel.MAPPED. I think the log is the obvious performance bottleneck and that’s where huge performance improvements can be made fairly easily.