we recently updated from 7.1.23 to 7.3.7
This came with an update from mysql 5.1.x to 5.6.x
Since then, we see a 20% higher load on the servers, where our applications are installed in combination with the mysqld (graph: https://www.dropbox.com/s/hzn4vzkdqg6vfhk/load_after_7.1.23_to_7.3.7_update.png?dl=0)
The first reason we thought of, was the lac of enginde_condition_pushdown=1|2 parameter in my.ini, but we checked, that the optimizer switch is set correctly to 'on' and our queries are still explaining to "Using where with pushed condition"
Any other thigs, which might have hit us?
The cluster seems to perform great. The CPU there went down, but as we also moved the data nodes to new and more and faster hardware, so this the was expected behaviour.
could the higher load on the mysqld be coming from the more data nodes (10 ->12) and more LQM (4->6) per data node?
Thanks for any hints.
Stefan
This came with an update from mysql 5.1.x to 5.6.x
Since then, we see a 20% higher load on the servers, where our applications are installed in combination with the mysqld (graph: https://www.dropbox.com/s/hzn4vzkdqg6vfhk/load_after_7.1.23_to_7.3.7_update.png?dl=0)
The first reason we thought of, was the lac of enginde_condition_pushdown=1|2 parameter in my.ini, but we checked, that the optimizer switch is set correctly to 'on' and our queries are still explaining to "Using where with pushed condition"
Any other thigs, which might have hit us?
The cluster seems to perform great. The CPU there went down, but as we also moved the data nodes to new and more and faster hardware, so this the was expected behaviour.
could the higher load on the mysqld be coming from the more data nodes (10 ->12) and more LQM (4->6) per data node?
Thanks for any hints.
Stefan