This is the full report of the run “Stage 2 of the latency programme: one-RTT votes, a 350 ms minimum header delay and the 40-minute chaos run”. Back to the run page.
r20261007-0316 · Fleet c3-hdb · c3-highcpu-8

Telcoin Network benchmark: mixed workload

Throughput is measured from blocks the chain produced (own senders vs every sender), resource use from Cloud Monitoring, Prometheus and the on-node sampler. Summaries cover the mixed phase. Hover any number for the JSON field it came from.

10 blaster(s), 6K senders, chain 32286, schema tn-blast-combined/v2 · mixed phase 2026-10-07 05:39–06:19 UTC · 1 observers, 10 validators

Preflight: WTEL from genesis (0x0000…37e1), v3 fee tier 3000, v4 available, Multicall3 present · Cooldown ended: idle_30s ×10

Headline numbers

Sustained mixed TPS (own)
6,909.7 tx/s
best 60-s mean of our own landed tx in the mixed phase
Sustained mixed TPS (chain)
6,909.7 tx/s
all tx in blocks, same window
Landed / accepted
99.7 %
14.3M of 14.4M accepted
Reverted (own)
0
0.00 % of landed
Latency p50
2,441 ms
submit → block timestamp; seen p50 8,084 ms
Latency p95
12,564 ms
seen p95 22,943 ms
Gas / s (own)
268M gas/s
chain 268M gas/s
Capacity at mix
11,256.8 tx/s
gas-limit basis 7,190.9 tx/s; block gas limit 30M

Per transaction type

Landed counts only our own senders; latency is submit → block timestamp.

TypeSubmittedAcceptedLandedRevertedUnlandedSkipsGas limitGas used avgp50p95
native_transfer4.01M4.01M4M07.79K024.1K21K2,423 ms12,440 ms
batched_self_send2.19M2.19M2.18M06.79K024.1K21K2,528 ms12,983 ms
uniswap_v2_swap1.98M1.98M1.97M05.58K0180K106K2,429 ms12,429 ms
stablecoin_transfer1.65M1.65M1.65M04.62K075K43.9K2,426 ms12,449 ms
wtel_wrap1.32M1.32M1.32M03.74K050K27.9K2,424 ms12,421 ms
wtel_unwrap881K881K879K02.53K045K35.2K2,427 ms12,514 ms
stablecoin_approve662K662K661K01.89K060K31.8K2,422 ms12,415 ms
uniswap_v2_add_liquidity440K440K439K01.21K0250K128K2,428 ms12,486 ms
contract_deploy330K330K329K09010140K74.2K2,431 ms12,472 ms
uniswap_v4_swap329K329K328K09840250K124K2,434 ms12,462 ms
uniswap_v2_remove_liquidity220K220K219K06230220K129K2,428 ms12,531 ms
uniswap_v3_swap219K219K218K06110220K120K2,430 ms12,480 ms
faucet_drip126K126K126K020424K150K107K2,232 ms15,563 ms

Submission by RPC node

NodeSubmittedAcceptedAccepted %Top errorsSend p50Send p95
bench-validator-01
bench-validator-01:8545
2.24M2.22M98.9 %known 14.6K9 ms29 ms
bench-validator-02
bench-validator-02:8545
1.08M1.03M95.7 %known 24.8K7 ms27 ms
bench-validator-03
bench-validator-03:8545
1.63M1.59M97.6 %known 20.2K8 ms31 ms
bench-validator-04
bench-validator-04:8545
1.56M1.53M98.1 %known 15.3K11 ms40 ms
bench-validator-05
bench-validator-05:8545
1.02M992K97.6 %known 11.8K, pool_full 7798 ms33 ms
bench-validator-06
bench-validator-06:8545
1.04M994K95.6 %known 25K8 ms30 ms
bench-validator-07
bench-validator-07:8545
1.86M1.83M98.2 %known 18.6K7 ms26 ms
bench-validator-08
bench-validator-08:8545
1.61M1.57M97.6 %known 19.9K8 ms30 ms
bench-validator-09
bench-validator-09:8545
1.73M1.7M98.2 %known 12.9K9 ms28 ms
bench-validator-10
bench-validator-10:8545
1.02M979K95.6 %known 24.6K7 ms26 ms

Throughput over time

Shaded: phases outside the mixed window. Hairlines: epoch closes. Dashed orange: chaos events.

Landed transactions per second

own senders vs chain total, per block-timestamp second

Gas per second

own vs chain gas used, per block-timestamp second

CPU and memory per node

CPU utilization

compute.googleapis.com/instance/cpu/utilization, 60-s mean, % of all vCPUs; summaries over the mixed phase

Table view
NodeClassMeanp95Peak 60-s meanMax
bench-observer-11observer15.4 %17.3 %17.8 %17.8 %
bench-validator-01validator35.8 %45.9 %48.7 %48.7 %
bench-validator-02validator34.7 %43.8 %45.4 %45.4 %
bench-validator-03validator35.2 %41.4 %43.4 %43.4 %
bench-validator-04validator34.9 %39.7 %43.7 %43.7 %
bench-validator-05validator27.3 %37.2 %46.1 %46.1 %
bench-validator-06validator35.4 %43.9 %51.0 %51.0 %
bench-validator-07validator35.2 %44.7 %47.8 %47.8 %
bench-validator-08validator35.0 %41.9 %43.4 %43.4 %
bench-validator-09validator35.3 %43.4 %46.6 %46.6 %
bench-validator-10validator35.2 %43.8 %47.0 %47.0 %

CPU: mean vs peak 60-s mean

One row per node, over the mixed phase.

telcoin resident memory

agent processes/rss_usage summed over telcoin pids; summaries over the mixed phase

Table view
NodeClassMeanp95Peak 60-s meanMax
bench-observer-11observer3.11 GiB4.25 GiB4.32 GiB4.32 GiB
bench-validator-01validator5.58 GiB7.30 GiB7.39 GiB7.39 GiB
bench-validator-02validator7.10 GiB9.16 GiB9.31 GiB9.31 GiB
bench-validator-03validator5.79 GiB7.52 GiB7.70 GiB7.70 GiB
bench-validator-04validator5.53 GiB7.87 GiB8.53 GiB8.53 GiB
bench-validator-05validator4.78 GiB6.45 GiB6.67 GiB6.67 GiB
bench-validator-06validator6.17 GiB8.90 GiB9.19 GiB9.19 GiB
bench-validator-07validator6.26 GiB8.65 GiB9.01 GiB9.01 GiB
bench-validator-08validator5.66 GiB7.54 GiB7.65 GiB7.65 GiB
bench-validator-09validator5.62 GiB7.39 GiB7.49 GiB7.49 GiB
bench-validator-10validator5.53 GiB7.29 GiB7.47 GiB7.47 GiB

telcoin RSS: mean vs peak 60-s mean

One row per node, over the mixed phase.

Memory used

agent memory/percent_used, state=used; summaries over the mixed phase

Table view
NodeClassMeanp95Peak 60-s meanMax
bench-observer-11observer10.2 %11.7 %12.0 %12.0 %
bench-validator-01validator28.0 %32.6 %33.2 %33.2 %
bench-validator-02validator37.9 %46.5 %47.7 %47.7 %
bench-validator-03validator29.4 %34.7 %34.9 %34.9 %
bench-validator-04validator27.3 %36.3 %38.6 %38.6 %
bench-validator-05validator21.7 %28.9 %31.3 %31.3 %
bench-validator-06validator32.2 %45.7 %46.6 %46.6 %
bench-validator-07validator32.2 %42.2 %42.6 %42.6 %
bench-validator-08validator28.6 %34.1 %34.3 %34.3 %
bench-validator-09validator29.7 %36.0 %36.3 %36.3 %
bench-validator-10validator28.0 %33.1 %33.9 %33.9 %

Memory used: mean vs peak 60-s mean

One row per node, over the mixed phase.

Disk

Disk throttling (validator)
not collected –
metric type unavailable in project
Disk performance degraded (validator)
none –
any sample

Disk read + write throughput

instance/disk/{read,write}_bytes_count rate, all devices; summaries over the mixed phase

Table view
NodeClassMeanp95Peak 60-s meanMaxLimit
bench-observer-11observer260.4 MiB/s411.6 MiB/s458.3 MiB/s458.3 MiB/s800.0 MiB/s
bench-validator-01validator188.1 MiB/s344.7 MiB/s369.4 MiB/s369.4 MiB/s800.0 MiB/s
bench-validator-02validator182.3 MiB/s310.8 MiB/s333.5 MiB/s333.5 MiB/s800.0 MiB/s
bench-validator-03validator187.4 MiB/s362.5 MiB/s404.5 MiB/s404.5 MiB/s800.0 MiB/s
bench-validator-04validator209.7 MiB/s388.0 MiB/s427.2 MiB/s427.2 MiB/s800.0 MiB/s
bench-validator-05validator158.8 MiB/s347.8 MiB/s379.9 MiB/s379.9 MiB/s800.0 MiB/s
bench-validator-06validator183.8 MiB/s351.4 MiB/s385.4 MiB/s385.4 MiB/s800.0 MiB/s
bench-validator-07validator196.3 MiB/s327.2 MiB/s360.1 MiB/s360.1 MiB/s800.0 MiB/s
bench-validator-08validator188.6 MiB/s304.3 MiB/s336.4 MiB/s336.4 MiB/s800.0 MiB/s
bench-validator-09validator172.6 MiB/s386.7 MiB/s428.0 MiB/s428.0 MiB/s800.0 MiB/s
bench-validator-10validator208.3 MiB/s414.9 MiB/s447.7 MiB/s447.7 MiB/s800.0 MiB/s

Disk read + write IOPS

instance/disk/{read,write}_ops_count rate, all devices; summaries over the mixed phase

Table view
NodeClassMeanp95Peak 60-s meanMaxLimit
bench-observer-11observer12.7K IOPS16.3K IOPS17.4K IOPS17.4K IOPS20K IOPS
bench-validator-01validator14.3K IOPS16.9K IOPS18.3K IOPS18.3K IOPS20K IOPS
bench-validator-02validator14.6K IOPS18K IOPS18.8K IOPS18.8K IOPS20K IOPS
bench-validator-03validator14.4K IOPS17.9K IOPS18.4K IOPS18.4K IOPS20K IOPS
bench-validator-04validator14.1K IOPS18.1K IOPS19K IOPS19K IOPS20K IOPS
bench-validator-05validator11.4K IOPS17K IOPS19.1K IOPS19.1K IOPS20K IOPS
bench-validator-06validator14.6K IOPS18.1K IOPS18.7K IOPS18.7K IOPS20K IOPS
bench-validator-07validator14.4K IOPS17.7K IOPS18.2K IOPS18.2K IOPS20K IOPS
bench-validator-08validator14.5K IOPS18K IOPS18.4K IOPS18.4K IOPS20K IOPS
bench-validator-09validator14.3K IOPS17.4K IOPS18K IOPS18K IOPS20K IOPS
bench-validator-10validator14.1K IOPS17.6K IOPS18.3K IOPS18.3K IOPS20K IOPS
Disk limits used
NodeMachinevCPUDiskIOPS limitMiB/s limitBasis
bench-observer-11c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-01c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-02c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-03c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-04c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-05c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-06c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-07c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-08c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-09c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget
bench-validator-10c3-highcpu-88hyperdisk-balanced 100 GB20K IOPS800.0 MiB/shyperdisk-balanced 100 GB: provisioned 20,000 IOPS, provisioned 800 MiB/s; c3 8 vCPU cap 50,000 IOPS / 800 MiB/s; reads and writes share this budget

Network

Network sent

instance/network/sent_bytes_count rate; summaries over the mixed phase

Table view
NodeClassMeanp95Peak 60-s meanMax
bench-observer-11observer1.1 Mbps1.3 Mbps1.4 Mbps1.4 Mbps
bench-validator-01validator98.1 Mbps113.0 Mbps134.8 Mbps134.8 Mbps
bench-validator-02validator95.3 Mbps111.5 Mbps149.2 Mbps149.2 Mbps
bench-validator-03validator95.8 Mbps113.3 Mbps119.0 Mbps119.0 Mbps
bench-validator-04validator94.4 Mbps115.7 Mbps115.8 Mbps115.8 Mbps
bench-validator-05validator76.2 Mbps114.6 Mbps120.0 Mbps120.0 Mbps
bench-validator-06validator92.6 Mbps110.5 Mbps112.1 Mbps112.1 Mbps
bench-validator-07validator97.1 Mbps119.7 Mbps124.3 Mbps124.3 Mbps
bench-validator-08validator96.0 Mbps120.2 Mbps124.2 Mbps124.2 Mbps
bench-validator-09validator95.8 Mbps116.6 Mbps119.4 Mbps119.4 Mbps
bench-validator-10validator92.7 Mbps110.4 Mbps120.8 Mbps120.8 Mbps

Network received

instance/network/received_bytes_count rate; summaries over the mixed phase

Table view
NodeClassMeanp95Peak 60-s meanMax
bench-observer-11observer6.2 Mbps5.9 Mbps53.9 Mbps53.9 Mbps
bench-validator-01validator10.1 Mbps12.8 Mbps13.1 Mbps13.1 Mbps
bench-validator-02validator8.2 Mbps10.3 Mbps10.9 Mbps10.9 Mbps
bench-validator-03validator9.1 Mbps11.1 Mbps11.5 Mbps11.5 Mbps
bench-validator-04validator9.0 Mbps11.4 Mbps11.8 Mbps11.8 Mbps
bench-validator-05validator11.3 Mbps20.7 Mbps53.9 Mbps53.9 Mbps
bench-validator-06validator8.9 Mbps10.3 Mbps35.4 Mbps35.4 Mbps
bench-validator-07validator9.5 Mbps11.9 Mbps12.1 Mbps12.1 Mbps
bench-validator-08validator9.2 Mbps12.1 Mbps14.4 Mbps14.4 Mbps
bench-validator-09validator9.5 Mbps11.8 Mbps14.2 Mbps14.2 Mbps
bench-validator-10validator8.9 Mbps12.0 Mbps35.8 Mbps35.8 Mbps

Consensus health

MetricQueryClassNodesMedian of node meansWorst peak 60-s meanMax
tn_primary_commit_latency_secondsp95validator103,864 ms29.0 s29.0 s
tn_engine_execution_duration_secondsp95validator103,870 ms15.8 s20.0 s
tn_engine_execution_duration_secondsp95observer13,243 ms5,558 ms6,750 ms
tn_worker_batch_size_bytesp95validator10240.4 KiB246.4 KiB246.4 KiB
tn_worker_batch_transactionsp95validator104861K1K
tn_executor_output_transactionsp95validator101K1K1K
tn_primary_consensus_output_bytesmaxvalidator10799.7 KiB2.1 MiB3.5 MiB
tn_primary_consensus_output_bytesmaxobserver1721.1 KiB1.6 MiB2.3 MiB
tn_engine_queued_outputsmaxvalidator102.377.758
tn_engine_queued_outputsmaxobserver11.884.258
tn_primary_roundmaxvalidator108371.76K1.78K
tn_primary_roundmaxobserver18321.75K1.77K
tn_primary_committed_roundmaxvalidator108351.76K1.78K
tn_primary_committed_roundmaxobserver18321.75K1.77K
tn_epoch_currentmaxvalidator106.517.258
tn_epoch_currentmaxobserver16.517.258
tn_batch_builder_pending_pool_transactionsmaxvalidator104028.9K8.9K
tn_batch_builder_pending_pool_transactionsmaxobserver1000
reth_process_resident_memory_bytesmaxvalidator105.76 GiB9.30 GiB9.32 GiB
reth_process_resident_memory_bytesmaxobserver13.16 GiB4.39 GiB4.40 GiB
tn_primary_subdags_committed_totalratevalidator100.6370.9721.09
tn_primary_subdags_committed_totalrateobserver1000
tn_primary_round_laglagvalidator102.9124.226
tn_primary_round_laglagobserver1000
tn_batch_builder_seal_failures_totalratevalidator500.01670.0222
tn_node_modemaxvalidator10011
tn_node_modemaxobserver1000

Commit latency p95

tn_primary_commit_latency_seconds

Round lag

tn_primary_round − tn_primary_committed_round

Engine queued outputs

tn_engine_queued_outputs, max by node

Certification by node

The share of each validator's own headers that formed a certificate, per window (tools/cert-rate.py on the node logs). bench-validator-02, bench-validator-06 and bench-validator-08 certified fewer than 90 % of their own headers in a window where they proposed at least 50. Own leader % is the validator's share of the committed leaders and not committed % the share of its certificates no committed leader reached, both over the run window; the fair share is 100 / 10 validators = 10.0 %. Greyed: fewer than 50 headers proposed, not judged.

ValidatorRegionarm a3checkarm stage2phase preamblephase warmupphase mixedphase cooldownrunOwn leader %Not committed %
bench-validator-01us-west2 (Los Angeles)99.899.199.399.497.699.899.513.20.6
bench-validator-02 below 90 %europe-west2 (London)97.997.789.193.794.4100.098.32.019.0
bench-validator-03australia-southeast1 (Sydney)99.998.897.198.996.7100.099.413.10.8
bench-validator-04asia-northeast1 (Tokyo)100.098.995.797.797.299.899.513.10.6
bench-validator-05northamerica-northeast1 (Montréal)99.598.798.698.995.3–99.310.61.7
bench-validator-06 below 90 %europe-west4 (Netherlands)82.296.5100.098.991.8100.088.31.020.7
bench-validator-07asia-southeast1 (Singapore)99.599.198.697.797.5100.099.412.80.6
bench-validator-08 below 90 %asia-east2 (Hong Kong)97.197.089.186.992.599.897.812.50.7
bench-validator-09asia-northeast3 (Seoul)99.497.598.698.393.199.898.713.00.5
bench-validator-10asia-south1 (Mumbai)99.497.291.392.792.6100.098.510.11.6

On-node sampler

NodeClassPeak RssAnonPeak RssFilePeak cachePSI memPSI ioPSI cpudb growthstatic_files growthRoot usedOOM Δ
bench-observer-11observer925 MiB3.84 GiB64 MiB 6.3 %0.0 %17.0 %0.7 %0 B4.13 GiB17.0 %0
bench-validator-01validator4.42 GiB3.05 GiB64 MiB 6.3 %0.1 %17.4 %10.8 %0 B4.13 GiB45.0 %0
bench-validator-02validator6.76 GiB2.75 GiB64 MiB 6.3 %0.0 %15.9 %10.2 %0 B4.13 GiB47.0 %0
bench-validator-03validator4.71 GiB3.06 GiB64 MiB 6.3 %0.1 %19.7 %9.8 %0 B4.13 GiB46.0 %0
bench-validator-04validator5.29 GiB3.03 GiB64 MiB 6.3 %0.0 %22.3 %10.4 %0 B4.13 GiB45.0 %0
bench-validator-05validator4.22 GiB3.07 GiB1.00 GiB 100.0 %0.0 %17.3 %16.1 %0 B3.95 GiB40.0 %0
bench-validator-06validator6.61 GiB2.79 GiB64 MiB 6.3 %0.1 %19.4 %10.4 %0 B4.13 GiB47.0 %0
bench-validator-07validator5.96 GiB3.07 GiB64 MiB 6.3 %0.1 %18.3 %11.1 %0 B4.13 GiB45.0 %0
bench-validator-08validator4.63 GiB3.19 GiB64 MiB 6.3 %0.1 %15.1 %10.4 %0 B4.13 GiB46.0 %0
bench-validator-09validator4.94 GiB2.70 GiB64 MiB 6.3 %0.3 %21.1 %10.5 %0 B4.13 GiB45.0 %0
bench-validator-10validator4.45 GiB3.07 GiB64 MiB 6.3 %0.0 %22.7 %10.7 %0 B4.13 GiB47.0 %0

RssAnon vs RssFile

/proc/<pid>/status of the telcoin process on the node with the largest RSS

consensus-db/cache size

du -sb of consensus-db/cache vs the 1 GiB ceiling

Pressure stall (some, avg10)

/proc/pressure on the node with the highest memory PSI

Headroom

Per role and per node, from sizing.json (p95 over the landed window; PSI and RssAnon max over the whole sampler run). The lines follow the hardware doc's tier rules: CPU p95 over 70 % of vCPUs; memory used p95 over 75 % of RAM, or telcoin RSS p95 over 85 % of RAM; disk write p95 over 60 % of the PD MiB/s limit, or write IOPS p95 over 60 % of the IOPS limit; IO pressure over 20 % or memory pressure over 5 % (PSI some avg10, max); network p95 over 50 % of 1 Gbps; root disk over 80 %. A line crossed on any node puts the role at the limit; a nonzero reading within 15 points of its line is tight; otherwise the role has headroom. OOM kills, disk throttling and degraded disk performance are flagged too.

SignalClassWorst nodeValueShare of capacityLineNodes over / tightStatus
CPU p95validatorbench-validator-0145.9 %45.9 %> 70 %0 / 0 headroom
Memory used p95validatorbench-validator-0246.5 %46.5 %> 75 %0 / 0 headroom
telcoin RSS p95validatorbench-validator-029.83 GB57.2 %> 85 %0 / 0 headroom
PSI memory maxvalidatorbench-validator-090.3 %0.3 %> 5 %0 / 8 tight
RssAnon peakvalidatorbench-validator-027.26 GB42.2 %info– info
Disk write p95validatorbench-validator-10446 MB/s53.1 %> 60 %0 / 6 tight
Write IOPS p95validatorbench-validator-0617,93389.7 %> 60 %10 / 0 at the limit
PSI io maxvalidatorbench-validator-1022.7 %22.7 %> 20 %6 / 4 at the limit
Root disk maxvalidatorbench-validator-0646.6 %46.6 %> 80 %0 / 0 headroom
Network p95validatorbench-validator-08120 Mbps12.0 %> 50 %0 / 0 headroom
Consensus cache peakvalidatorbench-validator-051.00 GiB100.0 %info– info
OOM killsvalidator––anyany– none
Disk throttlingvalidator––metric type unavailable in projectany– not collected
Disk performance degradedvalidator––any sampleany– none
CPU p95observerbench-observer-1117.3 %17.3 %> 70 %0 / 0 headroom
Memory used p95observerbench-observer-1111.7 %11.7 %> 75 %0 / 0 headroom
telcoin RSS p95observerbench-observer-114.56 GB26.5 %> 85 %0 / 0 headroom
PSI memory maxobserverbench-observer-110.0 %0.0 %> 5 %0 / 0 headroom
RssAnon peakobserverbench-observer-110.97 GB5.6 %info– info
Disk write p95observerbench-observer-11444 MB/s52.9 %> 60 %0 / 1 tight
Write IOPS p95observerbench-observer-1116,26281.3 %> 60 %1 / 0 at the limit
PSI io maxobserverbench-observer-1117.0 %17.0 %> 20 %0 / 1 tight
Root disk maxobserverbench-observer-1115.9 %15.9 %> 80 %0 / 0 headroom
Network p95observerbench-observer-116 Mbps0.6 %> 50 %0 / 0 headroom
Consensus cache peakobserverbench-observer-110.06 GiB6.3 %info– info
OOM killsobserver––anyany– none
Disk throttlingobserver––metric type unavailable in projectany– not collected
Disk performance degradedobserver––any sampleany– none

Per node

NodeClassCPU p95Memory used p95telcoin RSS p95PSI memory maxRssAnon peakDisk write p95Write IOPS p95PSI io maxRoot disk maxNetwork p95Consensus cache peak
Line> 70 %> 75 %> 85 %> 5 %info> 60 %> 60 %> 20 %> 80 %> 50 %info
bench-validator-01validator45.9 %32.6 %7.84 GB 46 %0.1 %4.75 GB 28 %377 MB/s 45 %16,653 83 %20.0 %44.0 %113 Mbps 11 %0.06 GiB 6 %
bench-validator-02validator43.8 %46.5 %9.83 GB 57 %0.0 %7.26 GB 42 %345 MB/s 41 %17,657 88 %20.4 %46.1 %112 Mbps 11 %0.06 GiB 6 %
bench-validator-03validator41.4 %34.7 %8.08 GB 47 %0.1 %5.06 GB 29 %404 MB/s 48 %17,735 89 %19.7 %45.1 %113 Mbps 11 %0.06 GiB 6 %
bench-validator-04validator39.7 %36.3 %8.45 GB 49 %0.0 %5.74 GB 33 %431 MB/s 51 %17,619 88 %22.3 %45.2 %116 Mbps 12 %0.06 GiB 6 %
bench-validator-05validator37.2 %28.9 %6.76 GB 39 %0.0 %4.67 GB 27 %386 MB/s 46 %16,753 84 %20.9 %38.8 %115 Mbps 11 %1.00 GiB 100 %
bench-validator-06validator43.9 %45.7 %9.56 GB 56 %0.1 %7.09 GB 41 %398 MB/s 47 %17,933 90 %21.1 %46.6 %110 Mbps 11 %0.06 GiB 6 %
bench-validator-07validator44.7 %42.2 %9.28 GB 54 %0.1 %6.40 GB 37 %377 MB/s 45 %17,556 88 %19.8 %44.6 %120 Mbps 12 %0.06 GiB 6 %
bench-validator-08validator41.9 %34.1 %8.09 GB 47 %0.1 %4.98 GB 29 %340 MB/s 41 %17,799 89 %19.0 %44.6 %120 Mbps 12 %0.06 GiB 6 %
bench-validator-09validator43.4 %36.0 %7.94 GB 46 %0.3 %5.30 GB 31 %429 MB/s 51 %17,002 85 %21.1 %44.3 %117 Mbps 12 %0.06 GiB 6 %
bench-validator-10validator43.8 %33.1 %7.83 GB 46 %0.0 %4.78 GB 28 %446 MB/s 53 %17,498 87 %22.7 %46.0 %110 Mbps 11 %0.06 GiB 6 %
bench-observer-11observer17.3 %11.7 %4.56 GB 27 %0.0 %0.97 GB 6 %444 MB/s 53 %16,262 81 %17.0 %15.9 %6 Mbps 1 %0.06 GiB 6 %

Small figures are the share of capacity: RAM for RSS, the PD limit for disk write (VM cap applied), 1 Gbps for network. Hover a cell for its JSON path.

Verdict

Fleet A vs Fleet B

A = Fleet c3-hdb · c3-highcpu-8 · r20261007-0316
B = Fleet c3-hdb · c3-highcpu-8 · r20261006-0458

Verdict

at the limit c3-highcpu-8 validators at 6,910 sustained TPS: at the limit on disk. Disk at the limit: write IOPS p95 16,653–17,933, up to 89.7 % of the 20,000 IOPS limit, over the 60 % line on all 10 validators (bench-validator-01, 02, 03, 04, 05, 06, 07, 08, 09, 10); IO pressure (PSI some avg10) max 20.4–22.7 %, over the 20 % line on 6 of 10 validators (bench-validator-02, 04, 05, 06, 09, 10); write p95 446 MB/s, 53.1 % of the 800 MiB/s limit (bench-validator-10), tight against the 60 % line. Memory tight: memory pressure (PSI some avg10) max 0.3 % (bench-validator-09), tight against the 5 % line. CPU has headroom: CPU p95 45.9 % of 8 vCPUs (bench-validator-01). Network has headroom: network p95 120 Mbps, 12.0 % of 1 Gbps (bench-validator-08). Next step: a faster volume (pd-ssd adds 30 IOPS and 0.48 MiB/s per GB up to the per-VM cap; past the cap, a larger VM).

at the limit c3-highcpu-8 observers at 6,910 sustained TPS: at the limit on disk. Disk at the limit: write IOPS p95 16,262, 81.3 % of the 20,000 IOPS limit on bench-observer-11, over the 60 % line; write p95 444 MB/s, 52.9 % of the 800 MiB/s limit (bench-observer-11), tight against the 60 % line; IO pressure (PSI some avg10) max 17.0 % (bench-observer-11), tight against the 20 % line. CPU has headroom: CPU p95 17.3 % of 8 vCPUs (bench-observer-11). Memory has headroom: memory used p95 11.7 % of RAM (bench-observer-11); telcoin RSS p95 4.56 GB, 26.5 % of 16 GiB RAM (bench-observer-11); memory pressure (PSI some avg10) max 0.0 % (bench-observer-11). Network has headroom: network p95 6 Mbps, 0.6 % of 1 Gbps (bench-observer-11). Next step: a faster volume (pd-ssd adds 30 IOPS and 0.48 MiB/s per GB up to the per-VM cap; past the cap, a larger VM).

at the limit c3-highcpu-8 validators at 5,953 sustained TPS: at the limit on disk. Disk at the limit: write p95 505–508 MB/s, up to 60.5 % of the 800 MiB/s limit, over the 60 % line on 2 of 10 validators (bench-validator-09, 10); IO pressure (PSI some avg10) max 26.4–32.2 %, over the 20 % line on all 10 validators (bench-validator-01, 02, 03, 04, 05, 06, 07, 08, 09, 10). Memory tight: memory pressure (PSI some avg10) max 0.0 % (bench-validator-03), tight against the 5 % line. CPU has headroom: CPU p95 31.3 % of 8 vCPUs (bench-validator-02). Network has headroom: network p95 103 Mbps, 10.3 % of 1 Gbps (bench-validator-06). Next step: a faster volume (pd-ssd adds 30 IOPS and 0.48 MiB/s per GB up to the per-VM cap; past the cap, a larger VM).

at the limit c3-highcpu-8 observers at 5,953 sustained TPS: at the limit on disk. Disk at the limit: IO pressure (PSI some avg10) max 29.3 % on bench-observer-11, over the 20 % line; write p95 475 MB/s, 56.6 % of the 800 MiB/s limit (bench-observer-11), tight against the 60 % line. CPU has headroom: CPU p95 20.3 % of 8 vCPUs (bench-observer-11). Memory has headroom: memory used p95 11.9 % of RAM (bench-observer-11); telcoin RSS p95 4.38 GB, 25.5 % of 16 GiB RAM (bench-observer-11); memory pressure (PSI some avg10) max 0.0 % (bench-observer-11). Network has headroom: network p95 9 Mbps, 0.9 % of 1 Gbps (bench-observer-11). Next step: a faster volume (pd-ssd adds 30 IOPS and 0.48 MiB/s per GB up to the per-VM cap; past the cap, a larger VM).

Validators: Fleet A (c3-highcpu-8) is at the limit on disk, tight on memory, with headroom on CPU and network; Fleet B (c3-highcpu-8) is at the limit on disk, tight on memory, with headroom on CPU and network. The same disk limit binds both fleets: every validator runs a 100 GB hyperdisk-balanced, which allows 20,000 IOPS on both; its throughput limit is 800 MiB/s on both. Disk is at the limit on both (Fleet A (c3-highcpu-8): write IOPS p95 17,933, 89.7 % of the 20,000 IOPS limit, IO pressure (PSI some avg10) max 22.7 %; Fleet B (c3-highcpu-8): write p95 508 MB/s, 60.5 % of the 800 MiB/s limit, IO pressure (PSI some avg10) max 32.2 %). Changing the machine shape did not clear it; the volume is the binding resource.

Observers: Fleet A (c3-highcpu-8) is at the limit on disk, with headroom on CPU, memory and network; Fleet B (c3-highcpu-8) is at the limit on disk, with headroom on CPU, memory and network. The same disk limit binds both fleets: every observer runs a 100 GB hyperdisk-balanced, which allows 20,000 IOPS on both; its throughput limit is 800 MiB/s on both. Disk is at the limit on both (Fleet A (c3-highcpu-8): write IOPS p95 16,262, 81.3 % of the 20,000 IOPS limit; Fleet B (c3-highcpu-8): IO pressure (PSI some avg10) max 29.3 %). Changing the machine shape did not clear it; the volume is the binding resource.

KPIFleet AFleet BB ÷ A
Sustained mixed TPS (own)6,909.7 tx/s5,952.9 tx/s0.86×
Sustained mixed TPS (chain)6,909.7 tx/s5,952.9 tx/s0.86×
Landed / accepted99.7 %99.6 %1.00×
Reverted (own)00–
Latency p502,441 ms3,383 ms1.39×
Latency p9512,564 ms17,983 ms1.43×
Gas / s (own)268M gas/s167M gas/s0.62×
Capacity at mix11,256.8 tx/s6,852.7 tx/s0.61×

Headroom, worst node per class

SignalClassFleet AFleet BLine
CPU p95validator45.9 % headroom31.3 % headroom> 70 %
Memory used p95validator46.5 % headroom50.6 % headroom> 75 %
telcoin RSS p95validator9.83 GB 57.2 % headroom10.31 GB 60.0 % headroom> 85 %
PSI memory maxvalidator0.3 % tight0.0 % tight> 5 %
Disk write p95validator446 MB/s 53.1 % tight508 MB/s 60.5 % at the limit> 60 %
Write IOPS p95validator17,933 89.7 % at the limit5,324 26.6 % headroom> 60 %
PSI io maxvalidator22.7 % at the limit32.2 % at the limit> 20 %
Root disk maxvalidator46.6 % headroom13.6 % headroom> 80 %
Network p95validator120 Mbps 12.0 % headroom103 Mbps 10.3 % headroom> 50 %
CPU p95observer17.3 % headroom20.3 % headroom> 70 %
Memory used p95observer11.7 % headroom11.9 % headroom> 75 %
telcoin RSS p95observer4.56 GB 26.5 % headroom4.38 GB 25.5 % headroom> 85 %
PSI memory maxobserver0.0 % headroom0.0 % headroom> 5 %
Disk write p95observer444 MB/s 52.9 % tight475 MB/s 56.6 % tight> 60 %
Write IOPS p95observer16,262 81.3 % at the limit2,101 10.5 % headroom> 60 %
PSI io maxobserver17.0 % tight29.3 % at the limit> 20 %
Root disk maxobserver15.9 % headroom14.3 % headroom> 80 %
Network p95observer6 Mbps 0.6 % headroom9 Mbps 0.9 % headroom> 50 %

Own TPS, trailing 60-s mean

aligned on each fleet's mixed-phase start

CPU, hottest validator

aligned on each fleet's mixed-phase start

Memory used, hottest validator

aligned on each fleet's mixed-phase start

telcoin RSS, hottest validator

aligned on each fleet's mixed-phase start

Disk MiB/s, hottest validator

aligned on each fleet's mixed-phase start

Network sent, hottest validator

aligned on each fleet's mixed-phase start

Reference chains

Not collected: reference chains.