|Table of Contents|
The purpose of this page is to surface documentation related to performance of the RChain platform
Performance goals for Mercury
|Mercury 1.0||1,000-1,500 COMM events/second in a single shard|
|Mercury patch||6,000 COMM events/second in a single shard|
When talking about performance on the RChain platform it is important to have clarity on definitions of terms related to performance. We recommend reading What does transaction mean for RChain as a first step for learning about the language of performance on the RChain platform.
Comm event - The completion of a send and receive of a message over a channel in the Rholang interpreter.
How to measure RChain platform performance
As a development team we use a performance test harness to evaluate the platform. Please see https://github.com/rchain/perf-harness for complete details on this testing environment.
When reporting on platform performance, we measure comm events/second running the Rholang contract intdupe.rho, a contract designed to create a large number of comm events on a wide range of channels, in the performance testing environment.
Note - Not all of this documentation reflects current planning and is indicated in the title with "(deprecated)". We keep this documentation here to preserve the history of this work.
|Content Report Table|
Work items in Jira