qhj348770376 commented on issue #5611: URL: https://github.com/apache/shardingsphere/issues/5611#issuecomment-634381961
> You didn't answer my question: **How do you judge the slow part is parse?** > > You are using a sharding-proxy or sharding-jdbc?  1、As can be seen from the screenshot, most of the performance loss is in SQL parsing 2、sharding-jdbc 4.1.0 From the list of historical issues, it can be found that the service timeout or slow response caused by the first analysis of SQL performance problems is a very clear problem. Other companies have the same problem. I think the official should not avoid this problem. It should be taken seriously. Help us solve this problem. If there are thousands of service QPS and hundreds of different SQL statements are parsed at the same time, this problem can be reproduced stably. And the official cache solution does not solve this kind of problem, the cache can only improve the resolution performance for the second time and later,not the first time . #2793 #5313 please!!! @terrymanu @tuohai666 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
