为什么值得关注

基准测试可通过一条命令完全重现，包含自动对比顺序状态根的验证以防止数据夸大，并证明签名验证和虚拟机不是性能瓶颈。

适合谁使用

评估Quantova的区块链开发者
性能工程师以分析执行引擎
验证节点运维人员评估终局性保障
研究状态机吞吐量的研究人员

典型使用场景

在本地硬件上验证Quantova节点吞吐量声明
比较不同工作负载下的执行与终局性特征
了解核心数对并行交易执行的影响
为部署规划建立基准性能基线

项目优势

通过单一bash命令可重现，并附带自动正确性检查
在包含热账户争用的真实工作负载下测量
签名验证和虚拟机吞吐量远高于执行吞吐量，将瓶颈定位在序列化状态访问
由于使用固定采样委员会，终局性不随验证者数量增长而扩展

使用前须知

吞吐量在Apple M4（10核，16GB）上测量，绝对数值因硬件而异
终局性在同机进程内测量，未包含真实网络传播延迟
所有测量仅为计算路径，不考虑生产网络开销

README 快速开始

Quantova throughput and finality

Reproducible benchmarks for the Quantova node. Every figure is produced by a harness that checks its parallel result against the sequential state root before it reports, and the throughput figures rerun on your own machine with a single command.

Headline

Around 44,000 transactions a second of execution throughput on a single node, and block finality under one second across a live validator committee. Signature verification and the virtual machine both run far above throughput, so the compute path keeps margin and the bound is serial state access.

Execution throughput

Measured on an Apple M4, ten cores, 16 GB, release build. The full block path runs a module lattice signature verify, a virtual machine transfer, and an account write back.

workload	parallel	speedup
independent transfers	47,712 tx/s	2.20x
a third contended on hot accounts	47,021 tx/s	2.14x
independent at half the cores	36,469 tx/s

Held constant over twenty seconds the floor is 41,431 a second and the median 44,085, so the figure is a rate the node sustains rather than a burst. Signature verification runs at 70,039 a second across the cores and the virtual machine alone at 1,381,895, both far past throughput, which places the ceiling on serial state access, the sparse Merkle state read and written in block order.

Block finality

Measured across a real four validator committee producing and finalising blocks one after another, each block built, attested, aggregated, and verified with a real finality certificate that every node checks.

percentile	finality
median	607 ms
p90	620 ms
p99	635 ms

Finality lands under a second, and it does not grow with the validator set. A fixed sampled committee carries it, so the certificate stays flat as validators join. This figure is the in process compute floor across the committee, a production network adds propagation between hosts on top.

Honest scope

Execution throughput is the compute path of one node. Finality is measured in process across the committee on a single host, so it is the compute floor and leaves out wide area propagation. Finalised throughput at production scale, with validators running in parallel across real hosts, is the figure the network is built to carry, and it is bounded by execution rather t

项目描述

Reproducible execution throughput benchmark for the Quantova node

Quantova-Benchmarks