You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Depending on the traffic patterns, sometimes it makes sense to enable compressed connection to the backend servers.
What
mysql_servers.compression is taken into account as the min_compress_length, the smallest package size for which compression will be enabled
backend connection code enables the compression options for the MariaDB client library when needed
Notes
Will create a follow-up issue for automated Docker test to see that the compression is indeed working. The idea for that is to check the amount of traffic on the network interface used by ProxySQL to communicate with the backend server before and after sending a big package with compression enabled. That big package should be easy to compress - something like REPEAT('a', 1048576).
The text was updated successfully, but these errors were encountered:
Why
Depending on the traffic patterns, sometimes it makes sense to enable compressed connection to the backend servers.
What
mysql_servers.compression
is taken into account as themin_compress_length
, the smallest package size for which compression will be enabledNotes
Will create a follow-up issue for automated Docker test to see that the compression is indeed working. The idea for that is to check the amount of traffic on the network interface used by ProxySQL to communicate with the backend server before and after sending a big package with compression enabled. That big package should be easy to compress - something like
REPEAT('a', 1048576)
.The text was updated successfully, but these errors were encountered: