makssent commented on issue #36972: URL: https://github.com/apache/shardingsphere/issues/36972#issuecomment-3467609347
> ShardingSphere-Proxy does indeed perform worse than ShardingSphere-JDBC, and ShardingSphere-JDBC will also be slower than a direct database connected (since it adds some new features). Based on past experience, ShardingSphere-Proxy can be over 30% slower than ShardingSphere-JDBC. We can explore ways to improve performance. If necessary, you may provide flame graphs to analyze where the performance bottlenecks are together. I understand and accept that. It’s logical that with a single shard, there’s an additional routing layer introduced by ShardingSphere, and in that case, Proxy will naturally perform slower than a direct database connection. However, as I understand it, this overhead should be compensated when the number of shards increases — for example, with 2, 4, 6, or 8 shards, where the load is distributed and the overall effect should balance out the routing costs. But according to our tests, we don’t see that happening: performance does increase, but not proportionally to the loss introduced by Proxy. With JDBC, on the other hand, everything works as expected — performance scales up and the improvement is noticeable. That’s why I wanted to ask — are there any articles, posts, or public results where someone has tested ShardingSphere-Proxy and achieved performance gains? Perhaps you or the community have conducted such experiments — I just haven’t come across any examples showing Proxy providing an actual performance improvement, only comparisons indicating that Proxy is slower than JDBC. Right now, we’re deciding whether to continue investing in improving Proxy or to focus on adapting the JDBC variant for our needs. Of course, we understand that performance depends on many factors — database size, number of shards, hardware configuration, and so on — but it would really help to see a real-world example where Proxy shows a performance improvement as the number of shards increases, compared to a regular database connection without ShardingSphere. That way, we could reproduce such an experiment, verify the results, and make further decisions based on that. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
