taosdata/TDengine

数据订阅 拉取耗时太长

Open

#33524 opened on Nov 10, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C (24,849 stars) (5,002 forks)batch import
help wantedquestion

Description

网络也正常

社区版 3.3.8.1

目前的架构是 6台服务器，其中5台tdengine server，第6台服务器 从其他5台通过数据订阅拉取数据， 每台服务器拉取开了5个线程，一共25个线程， 参数： properties.setProperty(TMQConstants.CONNECT_TYPE, "ws"); properties.setProperty(TMQConstants.CONNECT_USER, "root"); properties.setProperty(TMQConstants.CONNECT_PASS, "taosdata"); properties.setProperty(TMQConstants.AUTO_OFFSET_RESET, "latest"); properties.setProperty(TMQConstants.MSG_WITH_TABLE_NAME, "true"); properties.setProperty(TMQConstants.ENABLE_AUTO_COMMIT, "true"); properties.setProperty(TMQConstants.AUTO_COMMIT_INTERVAL, "1000");

5台服务器的数据库创建语句 CREATE DATABASE tpih PRECISION 'ns' KEEP 150 VGROUPS 10 CACHEMODEL 'both' DURATION 24h BUFFER 16;

Contributor guide

Tech stack
cjavasql
Domain
databaseperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Understanding of TDengine data subscription mechanismJava client configuration familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the data subscription pull performance issue reported in TDengine v3.3.8.1. The user experiences 17+ second delays when pulling data from 5 servers using 5 threads each (25 total). Relevant files may include the subscription client code (e.g., Java client using TMQConstants) and the server side subscription handling (likely in `source/libs/subscription` and `source/dnode/vnode`). Check if there are known bottlenecks in the WebSocket (ws) connection or serialization. Review comments #3 for potential follow up questions from maintainers. Do not provide a fix, only direction.