Release Notes and Announcements

Release Notes

Product Announcements

Product Introduction

Overview

Features

Strengths

Scenarios

Information Security

Regions and AZs

Product Feature List

Large version lifecycle description

MSSQL Compatible Version

Billing

Billing Overview

Instance Type and Specification

Purchase Methods

Refund

Overdue Payments

Backup Space Billing

Database Audit Billing Overview

Getting Started

Creating TencentDB for PostgreSQL Instance

Connecting to TencentDB for PostgreSQL Instance

Managing TencentDB for PostgreSQL Instance

Importing Data

Migrating Data with DTS

Kernel Version Introduction

Kernel Version Overview

Kernel Version Release Notes

Viewing Kernel Version

Proprietary Kernel Features

Database Audit

Audit Service Description

Activating Audit Service

View Audit Logs

Modify audit services

Audit Performance Description

User Guide

Instance Management

Upgrading Instance

CPU Elastic Scaling

Read-Only Instance

Account Management

Database Management

Parameter Management

Log Management and Analysis

Backup and Restoration

Data Migration

Extension Management

Network Management

Access Management

Data Security

Tenant and Resource Isolation

Security Groups

Monitoring and Alarms

Tag

AI Practice

Using the Tencentdb_ai Plug-In to Call Large Models

Building Ai Applications with the Tencentdb Ai Plug-In

Combining Supabase to Quickly Build Backend Service Based on TencentDB for PostgreSQL

Use Cases

postgres_fdw Extension for Cross-database Access

Automatically Creating Partition in PostgreSQL

Searching in High Numbers of Tags Based on pg_roaringbitmap

Querying People Nearby with One SQL Statement

Configuring TencentDB for PostgreSQL as GitLab's External Data Source

Supporting Tiered Storage Based on cos_fdw Extension

Implement Read/Write Separation via pgpool

Implementing Slow SQL Analysis Using the Auto_explain Plugin

Using pglogical for Logical Replication

Using Debezium to Collect PostgreSQL Data

Set Up a Remote Disaster Recovery Environment for PostgreSQL Locally on CVM

Read-Only Instance and Read-Only Group Practical Tutorial

How to Use SCF for Scheduled Database Operations

Fix Table Bloat

Performance White Paper

Test Methods

Test Results

API Documentation

History

Introduction

API Category

Making API Requests

Instance APIs

Read-only Replica APIs

Backup and Recovery APIs

Parameter Management APIs

Security Group APIs

Performance Optimization APIs

Account APIs

Specification APIs

Network APIs

Data Types

Error Codes

FAQs

Service Agreement

Service Level Agreement

Glossary

Test Results

PDF

포커스 모드

폰트 크기

마지막 업데이트 시간: 2024-08-09 15:24:42

This document will verify the performance data of TencentDB for PostgreSQL in write-only, read-only and read-write scenarios of Sysbench.
Scenario 1: Full Cache
In the full cache scenario, all data can be stored in the cache, so there is no need to read or write the disk to update the cache during the query process.
Write-only
Instance specifications
Concurrency
Single-table data size (table_size)
Total number of tables (tables)
QPS
TPS
1-core 2 GB memory
32
25000
64
21308.50
3551.41
4-core 16 GB memory
32
25000
64
139100.86
23183.37
8-core 32 GB memory
64
25000
64
219394.80
36565.50
48-core 480 GB memory
512
25000
256
357198.25
59531.89
Read-only
Instance specifications
Concurrency
Single-table data size (table_size)
Total number of tables (tables)
QPS
TPS
1-core 2 GB memory
32
25000
64
26327.01
1645.44
4-core 16 GB memory
32
25000
64
111475.78
6967.24
8-core 32 GB memory
64
25000
64
179257.13
11203.57
48-core 480 GB memory
512
25000
256
346572.52
21660.78
Read-write
Instance specifications
Concurrency
Single-table data size (table_size)
Total number of tables (tables)
QPS
TPS
1-core 2 GB memory
32
25000
64
17282.27
864.11
4-core 16 GB memory
32
25000
64
80646.27
4032.31
8-core 32 GB memory
64
25000
64
115549.05
5777.44
48-core 480 GB memory
256
25000
256
173502.17
8675.04
Scenario 2: Big Dataset
In the big dataset scenario, all data cannot be stored in the cache (the data size is more than twice the memory size), so the disk needs to be read and written to update the cache during the query process.
Write-only
Instance specifications
Concurrency
Single-table data size (table_size)
Total number of tables (tables)
QPS
TPS
1-core 2 GB memory
32
10000000
64
16973.36
2828.89
4-core 16 GB memory
32
10000000
64
64245.25
10707.54
8-core 32 GB memory
64
10000000
64
100686.77
16781.13
48-core 480 GB memory
256
10000000
640
125237.97
20873.00
Read-only
Instance specifications
Concurrency
Single-table data size (table_size)
Total number of tables (tables)
QPS
TPS
1-core 2 GB memory
32
10000000
64
14407.49
900.47
4-core 16 GB memory
32
10000000
64
58952.38
3684.52
8-core 32 GB memory
64
10000000
64
87727.56
5482.97
48-core 480 GB memory
512
10000000
640
137603.21
8600.20
Read-write
Instance specifications
Concurrency
Single-table data size (table_size)
Total number of tables (tables)
QPS
TPS
1-core 2 GB memory
32
10000000
64
13655.23
682.76
4-core 16 GB memory
32
10000000
64
58426.87
2921.34
8-core 32 GB memory
64
10000000
64
80741.40
4037.07
48-core 480 GB memory
256
10000000
640
114922.98
5746.15

도움말 및 지원

문제 해결에 도움이 되었나요?

더 자세한 내용은 문의하기 또는 티겟 제출 을 통해 문의할 수 있습니다.

피드백

Instance specifications	Concurrency	Single-table data size (table_size)	Total number of tables (tables)	QPS	TPS
1-core 2 GB memory	32	25000	64	21308.50	3551.41
4-core 16 GB memory	32	25000	64	139100.86	23183.37
8-core 32 GB memory	64	25000	64	219394.80	36565.50
48-core 480 GB memory	512	25000	256	357198.25	59531.89

tencent cloud

TencentDB for PostgreSQL

Test Results

Scenario 1: Full Cache

Write-only

Read-only

Read-write

Scenario 2: Big Dataset

Write-only

Read-only

Read-write

도움말 및 지원