I've come across some article online to enable mod_deflate to gzip files while sending from the server.
For that, I tried to load the mod_deflate.so module by adding a line on my httpd.conf
LoadModule deflate_module modules/mod_deflate.so
But it seems the mod_deflate.so file is missing from the server.
I tried a find / -name "mod_deflate.so" -print but it returns no results.
So how do I comp
I'm trying to build apache with mod_deflate enabled. When restarting apache I'm presented with the following error:
httpd: Syntax error on line 36 of /usr/local/apache/conf/httpd.conf: Cannot load /usr/local/apache/modules/mod_deflate.so into server: /usr/local/apache/modules/mod_deflate.so: cannot open shared object file: No such file or directory
How can I get mod_deflate.so?
I want to gzip my static files.
I am trying to load mod_expires.so and mod_deflate.so on my CentOS 5 server.
Here is my current server scenario.
I'm running on a Rackspace Cloud instance (16GB of RAM), using cPanel/WHM on a CentOS 5.5 install.
I'm currently running about 10 Magento sites, all varying in size (from medium size to small)
Over time I noticed the speed of the sites slowing down.
We run Apache on a FreeBSD system, it has multple web apps on it (Wordpress, Magento, custom PHP). As the traffic increases, we see more and more httpd processes in status "lockf" (using 'top'). The server load increases until we have to restart Apache.
As I understand this state Apache waits for a file lock. But how can we find out which file(s) are to be locked / cause the bottleneck?
I am trying to work out why my application keeps hitting the database while I have setup varnish infront of apache.
I have shared hosting through Justhost.
I am trying to load test an amazon centos instance sitting behind the amazon loadbalancer.
The application is written on php and uses the elastic cache and media is stored in s3 bucket.
When the server gets more than 1000 concurrent requests its starts giving "Apache interanl dummy connection" and the pages dont load when tried externally, even though the load uptime metric does not go beyond 1.