kimmking commented on issue #4341: shardingsphere 4.0.0 retrive very slow that sql script URL: https://github.com/apache/incubator-shardingsphere/issues/4341#issuecomment-587377554 @ancientelves After discuss with @terrymanu , I find the key point about this issue. The parameter `max.connections.size.per.query` in `server.yaml` is 1 by default. This means 16 sub query to each table one by one via a same connection. In my case, the cost is 250ms by proxy sharding, and came down to 90ms by set the parameter to 8, better than only one table. But a tip here : don't modify this parameter to a higher value in your production env, cause it maybe exhausted your jdbc connections in datasource pool.
---------------------------------------------------------------- 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] With regards, Apache Git Services
