[Feature] 用户使用ST存在效率较慢的情况 - Users may experience slow efficiency when using ST

[YOMO-Lee]

Search before asking

• I had searched in the feature and found no similar feature requirement.

问题详情

目前用户经常反馈使用ST的同步效率较低，有的甚至可能只有每秒几条，无法明确什么原因导致的，想提升效率总是无从下手
计划在ST中集成一个测试能力，该测试有以下想法
1、根据用户的配置文件拆分成两个，一个测试source端的瓶颈，一个测试sink端的瓶颈
2、根据用户的配置文件，测试两端的网络和读写峰值，然后可以结合目前的同步效率计算出一个速度达成率
3、根据以上结论得出一些建议
现在关于如何评估用户环境下同步的理论峰值，希望大家多给点建议

Description

At present, users often give feedback that the synchronization efficiency of using ST is low, and some may only have a few messages per second, making it difficult to determine the cause. It is always difficult to improve efficiency
We plan to integrate a testing capability in ST, which has the following ideas

1. Split the user's configuration file into two parts, one for testing the bottleneck on the source side and the other for testing the bottleneck on the sink side
2. Based on the user's configuration file, test the network and read-write peaks at both ends, and then calculate a speed achievement rate by combining the current synchronization efficiency
3. Based on the above conclusions, some suggestions can be drawn
   Now, regarding how to evaluate the theoretical peak of synchronization in user environments, I hope everyone can give more suggestions

Usage Scenario

Users may experience slow efficiency when using ST

Related issues

无

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[YOMO-Lee]

目前有一个方案：
就是编写代码来提供一个工具 分为三个部分，1. 引擎效率 运行fake to console的任务 计算任务效率 2. source效率，运行指定source to console的任务，计算效率 3. sink效率 运行fake to 指定sink的任务 计算效率