# A Cross-Chain Solution to Connect Multiple DNS Blockchains in Consensus Roots System
## 6 Experimental Evaluation
### Evaluation  
Transaction delay and transaction throughput are two key indicators in blockchain systems, so these two aspects need special attention when evaluating experimental performance. Transaction delay refers to the time interval from initiating a transaction on the blockchain to confirming the transaction as valid, which directly affects the confirmation speed of the transaction and the time efficiency of the entire cross-chain process. Transaction throughput refers to the total number of transactions that the blockchain system can handle in each unit of time, which is the total load of the blockchain system. To evaluate the performance of this cross-chain system, the system tests and evaluates indicators, such as the transaction delay, throughput, memory, and CPU consumption of the blockchain system on Hyperledger Caliper.  
Figure 5a,b show the relationship between the CPU usage and memory consumption and the transaction arrival rate (TPS) for different numbers of verification nodes (2, 4, and 6) in the relay platform of the system. As can be seen from Figure 5a, the CPU usage increased with the increase in the transaction arrival rate (TPS), which indicates that the system load also increases. Figure 5b also shows that the memory consumption (MB) increases with the increase in the transaction arrival rate (TPS), which indicates that the system resource consumption also increases. For the same TPS, the greater the verification nodes, the higher the CPU usage and memory consumption, which indicates that the number of verification nodes has an impact on the system performance, but not in a linear relationship. When the number of verification nodes increases to a certain extent, the system performance and resource consumption tend to stabilize or decline.  
Due to the involvement of multi-chain interaction and complex protocols, a cross-chain solution exhibits higher CPU and memory usage than existing DNS methods,  
Figure 5: The results of the CPU and memory usage: (**a**) CPU. (**b**) Memory.  
making it more suitable for scenarios with strong cross-chain interoperability requirements--particularly in addressing the risk of non-top-level domain (non-TLD) resolution nodes being blocked due to the centralized architecture of traditional DNS. Existing DNS methods demonstrate lower resource consumption in single-chain or single-network environments, making them ideal for scenarios prioritizing stability and lightweight operation, such as enterprise intranets and Kubernetes clusters. In the future, with the standardization of cross-chain technologies and improvements in hardware performance, the resource efficiency of cross-chain DNS solution is expected to gradually approach that of existing solutions.  
We tested the relay chain network with different numbers of nodes and TPS. The results are shown in Figure 6a,b. Figure 6a shows that the average delay was not affected by the number of nodes when the TPS was low, but it increased for six nodes when the TPS was high. This means that more nodes cause more congestion when there are many transactions. Figure 6b shows that the average throughput increased with the TPS, but it was lower for six nodes than for two or four nodes. This means that more nodes cause more overhead and inefficiency in data transmission and verification. Therefore, we conclude that the relay platform was stable in delay performance but not in throughput performance. We suggest to reduce the number of verification nodes in cross-chain applications to optimize the network efficiency.