apache / shardingsphere

Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.
Apache License 2.0
19.97k stars 6.75k forks source link

The TPS (Transactions Per Second) of the proxy has decreased by half. #33443

Open dobet opened 2 weeks ago

dobet commented 2 weeks ago

Question

For English only, other languages will not accept.

Before asking a question, make sure you have:

Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will close it.

use proxy 5.5.0 add a new module. test sysbench --> proxy --> mysql sysbench --> mysql

TPS,QPS decreased by half.

place help me see why ?

this is firegrpah, most in image

my module only litte image

this is global.yaml

props:
 system-log-level: INFO
 max-connections-size-per-query: 5
 kernel-executor-size: 16  # Infinite by default.
 proxy-frontend-flush-threshold: 128  # The default value is 128.
 # sql-show is the same as props in logger ShardingSphere-SQL, and its priority is lower than logging rule
 sql-show: false
 check-table-metadata-enabled: false
   # Proxy backend query fetch size. A larger value may increase the memory usage of ShardingSphere Proxy.
   # The default value is -1, which means set the minimum value for different JDBC drivers.
 proxy-backend-query-fetch-size: -1
 proxy-frontend-executor-size: 0 # Proxy frontend executor size. The default value is 0, which means let Netty decide.
 proxy-frontend-max-connections: 0 # Less than or equal to 0 means no limitation.
 proxy-default-port: 3307 # Proxy default port.
 proxy-netty-backlog: 1024 # Proxy netty backlog.

this is config.yaml datasources config

 connectionTimeoutMilliseconds: "30000"
        idleTimeoutMilliseconds: "60000"
        maxLifetimeMilliseconds: "1800000"
        maxPoolSize: 1000
        minPoolSize: 1000
terrymanu commented 6 days ago

I believe this is not a simple issue. Performance issue often involves a long list of issues that need to be investigated. I'm sorry, but based on your description, I am unable to provide the corresponding help.

If further assistance is needed, could you please provide additional analysis conclusions for discussion and reference?

dobet commented 3 days ago

我相信这不是一个简单的问题。性能问题通常涉及一长串需要调查的问题。很抱歉,但根据您的描述,我无法提供相应的帮助。

如果需要进一步的帮助,您能否提供额外的分析结论以供讨论和参考?

I test single table ,readwrite_splitting, and sharding feature. From the result that single only reduce %2, but other reduce 50%. I want to known why ? but I don't how to do

dobet commented 3 days ago

I test single table ,readwrite_splitting, and sharding feature. From the result that single only reduce %2, but other reduce 50%. I want to known why ? but I don't how to do

terrymanu commented 3 days ago

Can you find which specific method is slow, and whether the slowdown is due to the method itself being slow or due to lots of invocations?