https://github.com/wesql/wescale/blob/main/doc%2Fblogs%2FPerformance%20Comparison%20WeScale%20vs%20MySQL.md https://github.com/wesql/wescale/blob/main/doc%2Fblo

https://github.com/wesql/wescale/blob/main/doc%2Fblogs%2FPerformance%20Comparison%20WeScale%20vs%20MySQL.md https://github.com/wesql/wescale/blob/main/doc%2Fblogs%2FPer... Integrating WeSQL WeScale as a MySQL proxy may initially increase network latency due to additional round trips. However, as the load scales, it matches the throughput and latency of a direct MySQL connection. Connection multiplexing allows WeSQL WeScale to sustain high throughput under heavy loads, unlike MySQL, which may suffer performance drops due to too many connections consuming buffer pool memory. With read-write splitting enabled, WeSQL WeScale continues to scale linearly in throughput beyond MySQL's limits as test threads increase. The memory footprint of WeSQL WeScale is minimal in comparison to MySQL, and it only adds about one-third to the CPU overhead. For increasing queries per second (QPS), WeSQL WeScale's read-write splitting and horizontal scaling is more cost-effective than MySQL's vertical scaling.