makssent opened a new issue, #37569: URL: https://github.com/apache/shardingsphere/issues/37569
## Question Hi everyone, I’d like to clarify one nuance. As I understand it, scaling across nodes works as follows: we start with a single node that, условно, performs inserts using 6 threads. Then I scale the system to 2 nodes via ShardingSphere, and I effectively end up with two single nodes. The question is: how will the threads behave in this case? Will the Proxy distribute these 6 threads across the nodes (roughly 3 per node), or will each node effectively handle 6 threads? In the case where threads are “split,” it’s not entirely clear to me where a performance gain close to ×2 would come from. If the threads are divided, the load on each node becomes lower — that part is clear — but inserts are still executed with a total of 6 threads. In that case, it’s not completely clear what the point of having ×2 system capacity is if the total number of threads remains the same. Also, in sysbench tests that I’ve seen, the configuration on each node specified `HikariPool.minimumPoolSize = 200` and `HikariPool.maximumPoolSize = 200`, after which sysbench was run with `--threads=200`. Am I correct in understanding that in this scenario, and with this configuration, each node effectively receives 200 threads? -- 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]
