problem about memory usage about eAccelerator under php-fpm

Re: problem about memory usage about eAccelerator under php-fpm

etrader — Fri, 18 Nov 2011 23:20:09 -0500

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?

Re: problem about memory usage about eAccelerator under php-fpm

jamestanit — Mon, 06 Jun 2011 23:05:00 -0400

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

Adrenalin — Tue, 23 Jun 2009 22:02:08 -0400

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 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
>>
>> 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

Yorgo Sun — Tue, 23 Jun 2009 20:27:06 -0400

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

Re: problem about memory usage about eAccelerator under php-fpm

mike — Tue, 23 Jun 2009 12:21:20 -0400

or APC.

2009/6/23 Meto :
>
> 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.
>
>

RE: problem about memory usage about eAccelerator under php-fpm

Meto — Tue, 23 Jun 2009 06:01:28 -0400

Use xcache instead - i have no such problem.

---
Pozdrawiam,

Maciek `meto` W

problem about memory usage about eAccelerator under php-fpm

code_tin — Tue, 23 Jun 2009 03:30:44 -0400

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.