Last week i installed Google's Pagespeed on a CentOS/Apache 2.4 webserver to provide clients with a faster loading website. Although this seems to really help with a lot of sites, I am noticing one big drawback. The sites which have Mod_Pagespeed enabled have a significant increase in bandwidth usage. Where they used to generate around 100mb to 200mb of bandwidth a day, i am now seeing traffic easily going over 1000mb. This is of course a result of a Pagespeed setting that I probably have not set correctly.
i already am tinkering with some of the Pagespeed parameters and at the moment have it setup like this:
When going through the stats of the website i am noticing that by far the most bandwidth and pagehits are taken up by the internal Serf/1.3.9 (mod_pagespeed/1.13.35.2-0). This is however internal traffic and as far as i am concerned should not be counted as bandwidth usage. This leaves me with a couple of questions:
- What setting am i missing that is causing the 10 fold of bandwidth usage.
- How can i exclude the Serf traffic from ramping up the bandwidth tally.
- Is anybody else seeing this trend when using the combination of Cloudlinux/DirectAdmin/Apache/Pagespeed?
Kind Regards,
John.
i already am tinkering with some of the Pagespeed parameters and at the moment have it setup like this:
Code:
<IfModule !mod_version.c>
LoadModule version_module /usr/lib64/httpd/modules/mod_version.so
</IfModule>
<IfVersion < 2.4>
LoadModule pagespeed_module /usr/lib64/httpd/modules/mod_pagespeed.so
</IfVersion>
<IfVersion >= 2.4.2>
<IfModule !access_compat_module>
LoadModule access_compat_module /usr/lib64/httpd/modules/mod_access_compat.so
</IfModule>
LoadModule pagespeed_module /usr/lib64/httpd/modules/mod_pagespeed_ap24.so
</IfVersion>
<IfModule !mod_deflate.c>
LoadModule deflate_module /usr/lib64/httpd/modules/mod_deflate.so
</IfModule>
<IfModule pagespeed_module>
ModPagespeed on
AddOutputFilterByType MOD_PAGESPEED_OUTPUT_FILTER text/html
ModPagespeedFileCachePath "/var/cache/mod_pagespeed/"
ModPagespeedLogDir "/var/log/pagespeed"
ModPagespeedSslCertDirectory "/etc/pki/tls/certs"
ModPagespeedSslCertFile /etc/pki/tls/cert.pem
<Location /pagespeed_admin>
Order allow,deny
Allow from localhost
Allow from 127.0.0.1
Allow from 213.125.85.50
SetHandler pagespeed_admin
</Location>
<Location /pagespeed_global_admin>
Order allow,deny
Allow from localhost
Allow from 127.0.0.1
Allow from 213.125.85.50
SetHandler pagespeed_global_admin
</Location>
ModPagespeedStatisticsLogging on
ModPagespeedMessageBufferSize 100000
</IfModule>
ModPagespeedEnableFilters prioritize_critical_css
ModPagespeedEnableFilters defer_javascript
ModPagespeedEnableFilters sprite_images
ModPagespeedEnableFilters rewrite_images
ModPagespeedEnableFilters recompress_png
ModPagespeedEnableFilters convert_png_to_jpeg,convert_jpeg_to_webp
ModPagespeedEnableFilters collapse_whitespace,remove_comments
When going through the stats of the website i am noticing that by far the most bandwidth and pagehits are taken up by the internal Serf/1.3.9 (mod_pagespeed/1.13.35.2-0). This is however internal traffic and as far as i am concerned should not be counted as bandwidth usage. This leaves me with a couple of questions:
- What setting am i missing that is causing the 10 fold of bandwidth usage.
- How can i exclude the Serf traffic from ramping up the bandwidth tally.
- Is anybody else seeing this trend when using the combination of Cloudlinux/DirectAdmin/Apache/Pagespeed?
Kind Regards,
John.