You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "mlycore (via GitHub)" <gi...@apache.org> on 2024/07/06 08:31:14 UTC
[I] [DISCUSSION] ShardingSphere AutoScaling [shardingsphere-on-cloud]
mlycore opened a new issue, #489:
URL: https://github.com/apache/shardingsphere-on-cloud/issues/489
For stateful database connections between applications and ShardingSphere, it is always hard to scale the proxy to handle more long connections. If we scale the proxy horizontally, we cannot move the current long connection causing heavy load to move to new instances. The complexity and cost brought by this solution are way higher than letting it go. If we scale the proxy vertically, we can increase the CPU threshold and resolve overhead caused by computing. However, this idea cannot move to memory, since currently JVM is not capable of adjusting heap memory size in runtime.
--
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.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org