It’s impossible to expect the distributed storage software has the same speed as the underlying hardware, since it added the feature and high availability on top of the underlying hardware… Though we’re still in the process of tuning Longhorn. So far we haven’t spent much effort on performance since we want it to be easy to use and powerful first. Once it’s fully tuned you can expect much better performance.
And you can also try the other open source distributed storage softwares and see how they perform as well.
Another thing is the benchmark software makes huge differences, since there are many factors determined the speed of the storage. Which benchmark software you’re using?
Thank you for honest answer. You are right, every single layer of storage logic is cutting down performance. I was not seeking for IO from beginning but I noticed delays on my app stacks…
For sure will do, or wait for 1.0 of Longhorn itself
As some discussed above, longhorn is a distributed data storage, so some cost is required for atomic operations across replicas for crash consistency claim. In 1.1.0, data locality feature introduced, it supports best-effort mode to keep the mounted volume along with the replica/data, so it should provide some extra benefit in some conditions.
