taosdata/TDengine

execution time increases when using a thread pool for concurrent queries but remains normal when using a for loop

Open

#28,947 opened on Nov 27, 2024

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

Description

  • server版本：3.3.3.0 ，3节点

  • jdbc驱动版本：3.4.0，驱动类型：com.taosdata.jdbc.ws.WebSocketDriver

  • nginx 配置截图： image

  • 数据库连接池截图，最小100个连接： 1732699526(1)

  • 线程池配置截图，核心线程100个： image

  • 代码截图： image

  • 线程池执行耗时： image image image

  • for 循环执行耗时： image

单次大概有84个查询，多次对比查询均如此，线程池检索的耗时会逐渐增加

Contributor guide

Tech stack
cjavasql
Domain
backenddatabaseperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Java programmingJDBC basicsMultithreadingTDengine basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Examine the JDBC driver's WebSocketDriver implementation for potential blocking when used with a thread pool. Compare the thread pool and for loop approaches in terms of connection reuse and contention. Profile the execution time per query under both scenarios to identify the root cause. Check the driver version 3.4.0 for known issues.