Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27826
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain roze.lv designates 80.232.169.231 as permitted sender)
Message-ID: <006d01c74961$ae34f4f0$698df657@wired>
To: <internals@lists.php.net>
Date: Mon, 5 Feb 2007 22:10:27 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: FastCGI limit memory
From: r@roze.lv ("Reinis Rozitis")

Hello,
is there a chance that this will ever make in PHP5 (or othet future 
releases) as base feature http://www.zend.com/zend/week/pat/pat48.txt
That is besides PHP_FCGI_MAX_REQUESTS to have also the posibility limit the 
childs max memory usage/leak (PHP_FCGI_MAX_RAM_MB)

I'm asking about this just because yesterday while testing MagickWand ( 
http://www.magickwand.org  which according to Thomas Boutell 
http://marc.theaimsgroup.com/?l=php-dev&m=115698025320619 in some point 
should replace GD) just by accident discovered a huge leak in phpinfo() 
output of the extension.

Just by running some 100-1000 requests each of the php childs (10 total) 
memory usage grew up to ~1Gb but thats not the point (I'll try to valgrind 
and isolate the problem and send the bug to the MW developers).

My point is - although 5.2.x core has become much much better in memory 
management (4.4.x actually didnt really work without the patch) you can't 
say that there are no leaks in longer time span in all the bundled and not 
bundled extensions.
And although apache with its prefork is still a leader a lot of webservers 
which run php in fastcgi mode are getting more and more popular.

For example lighttpd according to NetCraft:

01.2007 lighttpd 172819
02.2007 lighttpd 702712

Besides looking at http://survey.netcraft.com/Reports/0702/ those which I 
know ( Zeus, lighttpd, nginx, LiteSpeed, Sun One) pretty all run PHP using 
fastcgi.

So how about it?

rr