“The performance metrics observed when factors such as real world network latency and packet loss are implemented indicate that TPS in EOS approaches levels comparable to Ethereum.”
So says a new study that claims to have completed the first independent benchmark testing of the EOS software.
While previously eos blockchain explorers have shown the network can handle more than 1,200 transactions a second, the study says it can actually handle only 250 transactions a second even under unrealistic conditions of no latency. They say:
“High levels of TPS are sustained at 0 ms round trip latency. When 50 ms of RTT is added into the system, performance immediately falls below 50 TPS indicating that latency has a significant effect on throughput. Once RTT is increased to 100 ms, performance drops even further.”
Round trip time (RTT) is the length of time it takes for a signal to be sent plus the length of time it takes for an acknowledgement of that signal to be received. That’s obviously not possible at zero seconds under real world conditions, with the authors so stating:
“The research results prove the inaccuracies in performance claims and concluded that the foundation of the EOS system is built on a flawed model.”
The study, funded by the Bounties Network which is led by Brent Xu of ConsenSys, replicated the eos network to analyze its performance during two months of testing. The conclusions it reached are fairly damning. They say, for example:
“There is no formal verification protocol that occurs to validate transactions beyond the fact that that block producers are including them within transactions.
The configuration of this system introduces further suspicion as mentioned in our performance testing on the fate of orphaned transactions that are not successfully processed by the network.
In Ethereum, orphaned and stale transactions are apparent for the network to see in the available mempool, while ec...