Geek Answers Handbook

What is the overhead of connecting to MySQL on small datasets?

Is there any significant overhead for enabling mysql connection compression for high-load databases, or is it always a winner?

We have databases that supply very small datasets back to the requesting program (PHP), but these databases occasionally receive very large bursts of traffic. If I enable link compression, will I probably see a significant performance hit on boot?

We use modern equipment, but not enough average server setup, that is, one or two dual-core processors, 8 GB of RAM, etc.

+4
source share
1 answer

In your situation it is impossible to say whether this will help or not. Just information is not enough. “Big traffic spikes from time to time” means a lot of small packets or a few very large packets or is it more related to the number of sql queries?

Are database servers remote machines? What is the bandwidth between the application server and the database, Lan Mbits, Gbits, Tbits. or WAN Kbits, Mbits.

Which means high load. Are you running out of processor resources, memory, IO disk, or bandwidth?

Some notes ...

  • Intensive cpu compression
  • Compression of large data sets has a bandwidth.
  • Compression on small data sets (what is small?) Is likely to only add a slight increase in CPU usage, but it will also only slightly improve throughput.
  • If your application and mysql server are on the same machine, I doubt that you will get any benefit from compression, because bandwdth is high, and compression and decompression require CPU resources.

Without shorter descriptions of the fact that conditions are difficult to give a short answer.

DC

0
source

More articles:


All Articles