Welcome! Log In Create A New Profile

Advanced

problem about memory usage about eAccelerator under php-fpm

Posted by code_tin 
The problem is:
every php-fpm child is stand alone process
so eA's shm_size will assign for every php child process.
if your shm_size is 64M
and you have open 200 PHP child
then you need 64M * 200 = 12800M RAM!!!
though it is VIRT,but you will use SWAP soon.
Use xcache instead - i have no such problem.

---
Pozdrawiam,

Maciek `meto` W
Re: problem about memory usage about eAccelerator under php-fpm
June 23, 2009 12:21PM
or APC.


2009/6/23 Meto <meto@xgame.pl>:
>
> Use xcache instead - i have no such problem.
>
> ---
> Pozdrawiam,
>
> Maciek `meto` Wójcikowski
> meto@xgame.pl
> http://xgame.pl
>
> -----Original Message-----
> From: highload-php-en@googlegroups.com
> [mailto:highload-php-en@googlegroups.com] On Behalf Of code_tin
> Sent: Tuesday, June 23, 2009 9:31 AM
> To: highload-php-en
> Subject: problem about memory usage about eAccelerator under php-fpm
>
>
> The problem is:
> every php-fpm child is stand alone process
> so eA's shm_size will assign for every php child process.
> if your shm_size is 64M
> and you have open 200 PHP child
> then you need 64M * 200 = 12800M RAM!!!
> though it is VIRT,but you will use SWAP soon.
>
>
if you use "top" to watch all the php processes. I think you said the column
is SHR. It means share memory. so, all the processes will share the memory,
not use 64M*200's RAM.
the RES is really physics memory used.

2009/6/23 code_tin

>
> The problem is:
> every php-fpm child is stand alone process
> so eA's shm_size will assign for every php child process.
> if your shm_size is 64M
> and you have open 200 PHP child
> then you need 64M * 200 = 12800M RAM!!!
> though it is VIRT,but you will use SWAP soon.
>



--
孙绍轩 Yorgo Sun
Maybe you should make shm_size lower in this case.
Do you really need 64M for every process ? Do you really need 200 child ?

On Wed, Jun 24, 2009 at 2:27 AM, Yorgo Sun<yorgosun@gmail.com> wrote:
> if you use "top" to watch all the php processes. I think you said the column
> is SHR. It means share memory. so, all the processes will share the memory,
> not use 64M*200's RAM.
> the RES is really physics memory used.
>
> 2009/6/23 code_tin <code.tin@gmail.com>
>>
>> The problem is:
>> every php-fpm child is stand alone process
>> so eA's shm_size will assign for every php child process.
>> if your shm_size is 64M
>> and you have open 200 PHP child
>> then you need 64M * 200 = 12800M RAM!!!
>> though it is VIRT,but you will use SWAP soon.
>
>
>
> --
>
Re: problem about memory usage about eAccelerator under php-fpm
June 06, 2011 11:05PM
I think he was right, the php-cgi will continue to consume memory - it is NOT SHR, it is RES.
Re: problem about memory usage about eAccelerator under php-fpm
November 18, 2011 11:20PM
Adrenalin Wrote:
-------------------------------------------------------
> Maybe you should make shm_size lower in this
> case.
> Do you really need 64M for every process ? Do you
> really need 200 child ?
>


How to set the memory for every process?
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 72
Record Number of Users: 5 on December 17, 2014
Record Number of Guests: 180 on December 21, 2014
Powered by nginx    Powered by FreeBSD    PHP Powered    Powered by Percona     ipv6 ready