Bug 60660 - Memory Limit
Summary: Memory Limit
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.5-HEAD
Hardware: PC All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Depends on:
Reported: 2017-01-28 16:46 UTC by Roberto Spadim
Modified: 2017-03-02 11:22 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Roberto Spadim 2017-01-28 16:46:17 UTC
Hi guys, could be possible implement a MAX MEMORY LIMIT in each WORKER?
for example... if one thread/process (thread/worker/etc...) consume more than Xbytes after a request, close the worker and open a new one, it's very usefull to avoid OOM

what i'm doing today is a php script executing this, if http apache process memory usage is bigger than X MB execute a KILL command to graceful-restart the process, this save me a lot of nights sleeping well
Comment 1 Roberto Spadim 2017-01-28 16:53:59 UTC
an example of "bandaid" solution:

Comment 2 Roberto Spadim 2017-01-28 16:56:33 UTC
others related comments about memory consume and apache
Comment 3 Reindl Harald 2017-01-29 12:55:14 UTC
these are mostly memleaks of modules like PHP and your kill command is far away from graceful beause you interrupt the request in a hard way - in other words what you want to see and do is nothing better as OOM killer which would kill the right processes if other services like mysqld are configured with OOMScoreAdjust=-1000

"MaxRequestsPerChild 50" would terminate each worker process *really* graceful after it handeled 50 requests and so the memleaks can't grow that far 

https://bugs.php.net/bug.php?id=73889 is one example of a memleak