- Trending Categories
- Data Structure
- Operating System
- C Programming
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
When should I use MySQL compressed protocol?
152 Lectures 16 hours
87 Lectures 5.5 hours
Let us understand when MySQL compressed protocol should be used −
The compression operation is used only if both client and server support ‘zlib’ compression, and the client requests compression.
The advantage of using compression is that it reduces the size of the payload.
On the other hand, the disadvantage of using compression is that it increases the computation time.
Performance benefits will depend largely on the size of the result set which is being sent.
In addition to this, the network bandwidth and latency between the database server and its clients also matters.
The larger the result set, the larger will be the latency.
In other words, the lesser the bandwidth, the more likely the user would see the benefit of compression.
The maximum level of service is limited to the smallest bottleneck. Hence, it is required to analyse the position regarding network and CPU resources in the current time.
The most optimized database server would utilize 100% of its CPU 100% of the time, otherwise the computing resources get wasted if it has a processor that is sitting idle.
- When Should I use Selenium Grid?
- When should I use a composite index in MySQL?
- Why should I use Hubspot?
- Which datatype should I use for flag in MySQL?
- When should I use the keyword ‘this’ in a Java class?
- What is a smart pointer and when should I use it in C++?
- Should I use COUNT(*) to get all the records in MySQL?
- How should I display MySQL database that is currently in use?
- When to use i++ or ++i in C++?
- When should you use 'friend' in C++?
- Which one should I use? The datetime or timestamp data type in MySQL?