Technical Roundup #17: Papyrus Network Performance Tests

Designing a highload B2B Blockchain Network is a fair challenge for our RnD department. The characteristics that may be acceptable in a B2C network turn out to be insufficient in the B2B segment, where demands on reliability, performance, data security, and other aspects are generally higher.

Today we will take a look specifically at the Network’s performance as we truly have something to tell, namely, how we managed to increase our network’s performance tenfold compared to Ethereum.

(Read more about Papyrus Network at https://papyrus.network/)

While the need to drastically increase productivity was obvious, the path to reach the solution required dozens of hours of research and testing. Many network-specific features are closely interrelated with each other; hundreds of tests were made to fine-tune them.

Firstly, we added transaction batching. This kind of transaction packaging lets us to drastically increase network performance without compromising security. In order to unlock the full potential of this approach, we also had to rework the queue sizes for pending and queued transactions. While these changes implied new changes in parameters of the maximum number of permissible transactions, and, most importantly, in the total number of transactions.

Finally, we overhauled buffers.

The result is a tenfold increase in performance. For multiple tests, we used a specific utility to load the network with 1500 transactions every second. The test results showed that the network successfully handles 1500 transactions per second and works stably at such a load for a long period of time. Below you can find the logs of the utility and the logs of the node. The logs show that all 1500 transactions fall into a block, which is generated every second. During the test, we used the type of configuration, suggesting the entire load to be applied to one gateway node, while the gateway-node is not engaged in the generation of blocks. Blocks are generated by several sealer nodes.

Test results:

Utility logs:

Node logs:

A visual representation, which can be seen on our monitor explorer (screenshot):

The test shows, that 1500 transactions fall into a block every second it is generated.

As a result, we got the desired and unique combination of a quality network. A comparative analysis is presented in this chart:

Read more at Papyrus Network: https://papyrus.network/

Now, that the testnet is deployed, we are happy to continue fine-tuning our network using it for a number of high-load applications.