If your DB load is high - I mean +50k/sec selects + 10k/sec inserts/updates/deletes - put your MaxScale on your "Web service" node(s). That saves extra network hop and increases performance approx 30%. Use also unix socket instead of TCP port for MaxScale listening port - that prevents exposing the listening port to network.
What i find more frustrating: this video is on the official MariaDB channel, and another user has to tell you how to get performance out of it. Seriously: clustering is not for beginners, therefore i thought i get more tips like the ones from @cyclomiha... 😞
If your DB load is high - I mean +50k/sec selects + 10k/sec inserts/updates/deletes - put your MaxScale on your "Web service" node(s). That saves extra network hop and increases performance approx 30%. Use also unix socket instead of TCP port for MaxScale listening port - that prevents exposing the listening port to network.
A really good tip. Thanks for sharing!
What i find more frustrating: this video is on the official MariaDB channel, and another user has to tell you how to get performance out of it.
Seriously: clustering is not for beginners, therefore i thought i get more tips like the ones from @cyclomiha... 😞
아주 좋아요 ㅎㅎㅎ