Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48093
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.221.191 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=fCnzpaOphvE135TMvtvK90Jrk9nVbhf1UzsQFyry0FQse81yn2gVf8eYp+qzoznKMj
         QhUqd66xZM5ik19ak721Y6VUA9hHd0fFD0VTUVZDY+YHKWuZAUQ+VI95jYbkOoeiVguv
         F5TEmK8yTPuBbf/7Gjvy3Wq14RVXrEKXTrH6M=
MIME-Version: 1.0
In-Reply-To: <36701B7BE4054FB3A72CFFB6B8A81DF5@KD5>
References: <j2g7b32197c1004060011n5b78f062kf05bde7d0b2b9993@mail.gmail.com>
	 <4BD54437.2020304@daylessday.org>
	 <q2j3bea96c41004260115iac33d39fnb7d303794997acf5@mail.gmail.com>
	 <4BD54D42.5070400@daylessday.org>
	 <y2v3bea96c41004260238t4168458epe09f61d056cedc03@mail.gmail.com>
	 <4BD564A9.2060000@daylessday.org>
	 <n2g3bea96c41004260308m13b1571fn321d86afdf520297@mail.gmail.com>
	 <4BD57525.50803@daylessday.org>
	 <t2j3bea96c41004260418p6eb184bco599bc352be517433@mail.gmail.com>
	 <36701B7BE4054FB3A72CFFB6B8A81DF5@KD5>
Date: Mon, 26 Apr 2010 23:20:41 +0800
Message-ID: <n2g7b32197c1004260820zb1fa39bdvfb0bf8c13ff61f83@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=00c09fa21a7aee611b0485255189
Subject: Re: [PHP-DEV] One suggestion to PHP-FPM
From: tly.phpfans@gmail.com (looyao teng)

--00c09fa21a7aee611b0485255189
Content-Type: text/plain; charset=ISO-8859-1

Thanks for your continuing discussions, as the person who
 gave this suggestion,  I want to express my ideas.
1. The focus of this suggesting is that to free
the occupied memory in order to memory can be used
 efficiently, at the same time, system have more free memory
to allocate. This has noting to do with how many memory the
 server has, usually our server have 16GB memory, and sometimes
our server also crashes. Though this requirement my be associated
with the error handler of Imagick self,  our aim is to let it run
 more valueable. And other circumstances maybe have this problem ,
such as large data operating, and the occupied memory will not
be freed until the process exit.
2. The PHP's management of memory can't give the occupied memory
back to the system by itself.
3.Though the idea is good,it cannot acquiret the actual state of
 the memory usage of the process for PHP. Meanwhile,the other
methods are not good enough in a way,such as cannot run on
multi-platform.So we hope to try to monitor and manage the heap
memory.After all,the used memory of PHP itself is relatively
stationary.And the memory_limit  is ought to limit the heap memory.
So, when it go beyond the limit,kill the process in order to release
 the memory.
4. I'm agree that it's not necessary to realize this feature in
SAPI, but it may be not easy to realize in other pleaces, because
 it  must check after current task execute, and SAPI is not all like
 FPM that is independent process existing.
5. Now that FPM is one process manager , it allows work processes
exit after excuting some times, and it kills work processes according
 to the memory usage is the similar requirement.
6. I do not install memtrack, according to the README, I think it's
not my really want , the focus of my requirement is not to log or
throw exception, because I know my problem is what, I need to solve
it, and the solution is to exit.
7. Now our solution to handle this problem is
  (1) control max_requests little as possible
  (2) control memory_limit low as possiable
  (3) write a shell , check the process usage, kill it when memory
  out of limit.
and we think if this suggestion could be accepted, wo can let config
 more easy , at the same time, memory can be use more efficiently.
Because shell maybe kill the process which is handling request.

I also hope that it can be realized in SAPI or other places,  before
there is no more better solution, first to achieve this relatively
short-term solution.

--00c09fa21a7aee611b0485255189--