Token swap in progress: Swap Guide

Все новости

Load Test Description



We are happy to announce Credits platform capacity and bandwidth test. Our team understands the significance of this step and we are going to conduct it in most credible way. The process will be divided in three stages which will be performed step by step.


 1. Internal load testing

 2. External load testing

 3. Stress-test


Internal load test - testing, which is conducted to determine how quickly the network operates under a certain load. Aimed to check and confirm system attributes such as scalability, reliability and resource consumption, it will be carried out exclusively using the resources of the Credits team. Outside parties will not participate at this stage.


External load testing will be carried out with the help of community members. Everybody will be allowed to participate and run a node. We are planning to engage KOLs and Credits advisors to take part as well.


Stress-test - software testing type which is aimed to evaluate reliability and stability of the system in conditions of exceeding the limits of normal operation. We will test how consensus protocol, transport protocol and database are working under critical conditions.


In this article we will share information about process and environment of internal load test . We also will determine points which will be included in test report to facilitate correct understanding of future results. Сommunity can follow testing process in real time mode. According to our calculations testing process will take approximately 2 hour.


General information


Load capacity test of Credits decentralized blockchain platform will be conducted strictly according to the requirements stated in this document.


We have several aims to be determined during testing process:

  • Peak network capacity which will be measured in transactions per second;

  • Peak network bandwidth;

  • Pattern of platform capacity with network load increase


Testing process:


  • Network is loaded with the help of internal transaction generator which is a programming code added to network node and working directly with other network nodes. Transaction goes directly from node to network and then in pool of new round transaction waiting for verification which is processed on main node;

  • There will be 5 nodes in network which will generate transactions;

  • Network load will be increasing by 275 transaction per second, 11 transactions for every round from every transaction generator node;

  • Network load will continue until its full inoperative failure or until the moment of when peak system load will be achieved in transactions adding and processing.


Testing stages


1. Each of 5 network nodes generates 1 thousand transactions, others nodes are designated to support operational capability

2. Transactions of further or previous round are collected on main network node;

3. Main node sends the pool of received transactions to trusted nodes;

4. Trusted nodes validate and verify transactions;

5. The node which will add current block to storage signs it. This block has transactions from the previous pool which were validated during the previous step;

6.The node which is adding transaction in current round sends block to all network nodes to  form a table of nodes able to participate in the new round

7. After this process is finished new round of receiving, validation and verification of transactions begins.

Testing environment


During the testing process we will use the following equipment:



Model: Intel Xeon
Processor: 2x E5-2670 (2.6 Ghz) 16 (32 T)
Hard Disk: 2x 500GB SSDs 1x 4TB HDD
Network: 10Mbps burstable


Model: Intel Xeon

Processor: Dual (2x) Intel Xeon Hexa Core E5-2630L 2.0GHZ, Turbo 2.5Ghz, (12core, 24thread)


Hard Disk: 2TB SATA

Network: 1Gbps burstable


Model: Intel Xeon

Processor: E3-1270v8


Hard Disk: 2TB SATA

Network: 1Gbps burstable


Model: DELL R410
Processor: 2 CPU X5650
Hard Disk: 1TB SATA
Network: 1Gbps burstable


Model: DELL R410
Processor: 2 CPU X5650
Hard Disk: 1TB SATA
Network: 1Gbps burstable

Total amount of virtual machines: 32


Virtual machines with following characteristics:

  • 2 cores

  • 8 Gb ram

  • 100 Gb storage

  • 64bit processor   

 1.  Australia - Linux

  • External address 116.***.***.3

  • 8 virtual machines set up

2. Korea

  • External address 103.***.***.55

  • 8 virtual machines set up

3. Canada - white adresses as an example of using IPv6 technology

  • 167.***.***.220   02:00:00:f3:50:67

  • 167.***.***.221   02:00:00:15:6b:d7

  • 167.***.***.222   02:00:00:a2:a0:78

  • 167.***.***.223   02:00:00:1d:55:e0

4. Latvia

  • External address 89.***.**.168

  • 6 virtual machines set up

5. Germany

  • External address 37.***.**.36

  • 6 virtual machines set up

Testing report


Two scenarios are possible over the course of the testing, that would allow to make a generalised conclusion.

1. The network may stabilise at a certain level and will continue to showcase stable operation upon reaching a certain extreme load level. Under this scenario the testing will be considered as passed

2. The network may stop being operational upon reaching a certain extreme load level. Under this scenario the testing will be considered as failed.


Two main sources of information - Credits Monitor and Windows/Linux system monitor will be used as a final report on the results of the load test.


Credits Monitor:

  • Number of transactions in one block

  • Number of transactions per second

  • Number of nodes in the network

  • Dynamics of the network performance over the course of the gradual load increase (display of blocks being added)  


Windows/Linux Monitors:

  • CPU Load

  • Hard drive load

  • Data volume on the hard drive

  • Network channel load

  • Used RAM volume




Internal load test will happen at the beginning of September. Exact date will be announced in advance for people to follow it in real time mode. After publication of Stage 1 testing report we will shortly announce the date of public load test. Every stage of testing will have its own reports and whole testing process report at the end. Stay tuned, guys!

Share: twitter logo facebook logo reddit logo linkedin logo