New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to set maximum size of a resource for mod_pagespeed to optimize #501

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 4 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Apr 6, 2015

From a user report:

if there is a request for a huge file then mod pagespeed goes for a spin and 
the RAM usage bloats up. Is there a way to tune this, or ask modpagespeed to 
not process if the response size is bigger than a certain limit. Currently we 
are handling by having a cron that kill any httpd process that exceeds a 
certain RAM usage size. 

Original issue reported on code.google.com by jmara...@google.com on 19 Sep 2012 at 12:35

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Original comment by jmara...@google.com on 19 Sep 2012 at 12:35

  • Changed state: Accepted
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Original comment by jmara...@google.com on 30 Oct 2012 at 9:58

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Original comment by matterb...@google.com on 10 Dec 2012 at 8:13

  • Added labels: Milestone-v24, release-note
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Add "ModPagespeedMaxCacheableContentLength" to the configuration options.

Original comment by hui...@google.com on 10 Dec 2012 at 8:17

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment