Is there a significant overhead for starting a connection compression of mysql for a high load database or is it always a winner? ?
We have databases delivering back to a very small dataset requesting program (PHP) but these databases get periodic traffic formations. If I turn on the connection compression, then I am likely to see a significant drop in performance under load?
We are using modern hardware but this is not a fairly average server setup, i.e. one or two dual-core CPUs, 8GB RAM, etc.
There is no way to state in your situation, if it will help or will not help. Just not enough information. Does "big burst of traffic from time to time" mean very small packets or some very large packets or is it related to the number of SQL queries?
What are the database servers on the remote machine?
What is the bandwidth between applications and database servers, LAN MBTs, GBs, TBs, I or Van Kebits, MBT?
What does "high load" mean? Are you running out of CPU resources, memory, disk IO or bandwidth?
Some notes ...
- Compression CPU is intensive
- Compression large datasets are bandwidth friendly
- Compression on small datasets (Which is small?) Probably only add a negligible increase in CPU usage, but it will only improve the bandwidth delicately
- If your app and mysql server are on the same machine I suspect that You will get some benefit from compression, because bandwidth is high and compressed Non and Decompression requires CPU resources.
Without more brief description
DC
Comments
Post a Comment