The most relevant performance measures for user experience with Orbis are throughput and latency.

Latency is the amount of time between a user initiating action and the action is completed. Whereas, throughput is the number of user interactions that can be processed in a given time period.

The latency of a concurrent process is greater than or equal to the sum of the durations of the longest chain of steps in the process. For example; adding funds to or removing funds from the rollup is limited by the throughput and latency of the blockchain (Cardano). However, latency on Orbis itself for transactions would not be limited by Cardano and would be shorter.

When it comes to the throughput, the Orbis architecture should be able to scale to any level that the market would support. This will be achieved in a series of iterations in which different limiting factors are incrementally improved to achieve the level of scale that the market demands.

In contrast to the EVM, the eUTXO model of Cardano allows for a local state for the smart contracts and parallel execution of transactions. Because of this zk-rollups on Cardano can achieve a better throughput than Ethereum Virtual Machine (EVM)-based zk-rollups.

Last updated