Help Center/ TaurusDB/ Performance White Paper/ Performance Data/ Write-only Mode
Updated on 2026-11-03 GMT+08:00
View PDF
Share

Write-only Mode

Dedicated DB Instance Test Data

Table 1 Test data in write-only mode (x86 architecture, multi-AZ deployment)

Mode

Tables

Table Rows

Threads

Instance Specifications

TPS

QPS

Write-only

250

25,000

128

2 vCPUs | 8 GB

5,473.22

32,839.34

128

2 vCPUs | 16 GB

5,685.26

34,111.57

256

4 vCPUs | 16 GB

16,312.03

97,872.16

256

4 vCPUs | 32 GB

17,025.3

102,151.81

512

8 vCPUs | 32 GB

30,702.7

184,216.21

512

8 vCPUs | 64 GB

32,941.36

197,648.16

512

16 vCPUs | 64 GB

55,022.87

330,137.28

512

16 vCPUs | 128 GB

61,818.75

370,912.52

512

32 vCPUs | 128 GB

73,708.67

442,252.03

512

32 vCPUs | 256 GB

75,602.57

453,615.46
Table 2 Test data in write-only mode (Arm architecture, multi-AZ deployment)

Mode

Tables

Table Rows

Threads

Instance Specifications

TPS

QPS

Write-only

25

250,000

128

2 vCPUs | 8 GB

2,717.45

16,304.67

256

4 vCPUs | 16 GB

9,098.34

54,590.03

512

8 vCPUs | 32 GB

19,617.14

117,702.85

1,000

16 vCPUs | 64 GB

32,862.55

197,175.31

1,000

32 vCPUs | 128 GB

43,750.68

262,504.08

1,000

60 vCPUs | 480 GB

47,608.14

285,648.87

Dedicated DB Instance Test Results

Figure 1 Test results in write-only mode for different specifications (x86)
Figure 2 Test results in write-only mode for different specifications (Arm)
Parent topic: Performance Data