You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2022/12/27 02:40:06 UTC

[GitHub] [shardingsphere] TeslaCN commented on issue #8527: sharding-proxy performance

TeslaCN commented on issue #8527:
URL: https://github.com/apache/shardingsphere/issues/8527#issuecomment-1365564770

   We have tried using Vert.x in ShardingSphere-Proxy. And I have tried integrate [ShardingSphere with Vert.x API](https://github.com/TeslaCN/shardingsphere-vert.x). But the improvement is not as large as expected.
   Finally we found the I/O performance was not the key of performance issue. The CPU cost of calculation route, rewrite is the largest bottleneck of performance. 
   At present, we are trying to reduce CPU cost of kernel. Such as https://github.com/apache/shardingsphere/issues/21223.
   SInce this issue has been inactive for a while, I'm closing it for now.


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org