Limit the number of Apache httpd processes using software, thus reducing resource usage and improving website performance.
Apache::GTopLimit is a Perl module that is compatible with platforms supported by GTop.pm, which is a Perl interface to libgtop. It responds to questions that were asked on the mod_perl mailing list regarding how to instruct the httpd process to exit if certain conditions are met. These conditions include exceeding a specified memory size limit, having a shared memory size below a specified limit, or having unshared memory size above a certain limit.
With the help of this module, you can kill Apache httpd processes that are too large or have too little shared memory. You can choose to set up the process size limiter to check the process size on every request. In your startup.pl, you need to use Apache::GTopLimit, and specify the maximum process size, minimum shared process size, and maximum unshared process size in KB. You can also set up the debug mode and register a handler in your httpd.conf.
You can check requests that are likely to get big or unshared, which makes it easier for those who are mostly running Apache::Registry scripts. In your handler/CGI script, you can use Apache::GTopLimit and set the maximum process size, minimum shared process size, or maximum unshared process size. Note that the MAX_PROCESS_SIZE, MIN_PROCESS_SHARED_SIZE, and MAX_PROCESS_UNSHARED_SIZE are independent, and each will be checked only if it is set.
To minimize overhead, you can specify the number of times to check the process size using $Apache::GTopLimit::CHECK_EVERY_N_REQUESTS. This will only check the process size every other time the process size checker is called. Finally, it is better not to mix MAX_PROCESS_UNSHARED_SIZE with the first two.
With the help of this module, you can kill Apache httpd processes that are too large or have too little shared memory. You can choose to set up the process size limiter to check the process size on every request. In your startup.pl, you need to use Apache::GTopLimit, and specify the maximum process size, minimum shared process size, and maximum unshared process size in KB. You can also set up the debug mode and register a handler in your httpd.conf.
You can check requests that are likely to get big or unshared, which makes it easier for those who are mostly running Apache::Registry scripts. In your handler/CGI script, you can use Apache::GTopLimit and set the maximum process size, minimum shared process size, or maximum unshared process size. Note that the MAX_PROCESS_SIZE, MIN_PROCESS_SHARED_SIZE, and MAX_PROCESS_UNSHARED_SIZE are independent, and each will be checked only if it is set.
To minimize overhead, you can specify the number of times to check the process size using $Apache::GTopLimit::CHECK_EVERY_N_REQUESTS. This will only check the process size every other time the process size checker is called. Finally, it is better not to mix MAX_PROCESS_UNSHARED_SIZE with the first two.
What's New
Version 1.02: N/A