Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have zlib and Zend Optimizer enabled on my server and I have read about the
zlib.output_compression
directive. Are there any caveats with turning this directive in my server?
First you should determine what the bottleneck is (or will probably be under load).
With turning on (transparent) compression you trade cpu resources for data (network) throughput. So, you have to think about: Is my data (highly) compressible? Is the time it takes to transfer the data to the client a bottleneck? How much cpu resources can I spent for the compression? What other resources does my script use (e.g. memory consumption, database connections, …)? Which resource will become the bottleneck under (heavy) load? When, where and for how long will one instance of the script block another instance? And so on and on.
You might also be interested in tools like YSlow, profilers like the one built into xdebug, the apache benchmarking tools, (code) caches like apc …and many more.