Re: Fw: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 06, 2001 4:10 AM Subject: Re: Fw: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed. > As Hartmut said, this argument is invalid in the Apache environment. All > the static code in Apache is loaded to memory only once (in copy-on-write

Re: Fw: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

can also reduce the KeepAlive timeout value to help-out. > > > > > >Jason > > > > > > > > > > > > > > > > ----- Original Message - > > > > From: "Rasmus Lerdorf" <[EMAIL PROTECTED]> > > > &

Re: Fw: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

shared libraries save memory (and disk space) if and only if they are used by different programs simultaneously in the case of apache there is usually no such gain as apache is started only once and then creates its process farm using fork(), so that all theese processes share their code and st

Re: Fw: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

n apache child. > >You can also reduce the KeepAlive timeout value to help-out. > > > >Jason > > > > > > > > > > > > - Original Message - > > > From: "Rasmus Lerdorf" <[EMAIL PROTECTED]> > > > To: "F

Re: Fw: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

You can also reduce the KeepAlive timeout value to help-out. > >Jason > > > > > > > > - Original Message - > > From: "Rasmus Lerdorf" <[EMAIL PROTECTED]> > > To: "Filip Sielimowicz" <[EMAIL PROTECTED]> > > Cc: <[

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

On Mon, Jan 29, 2001 at 06:23:56PM -0600, Brian Moon wrote: > Ok, so what are the benefits of not returning memory to the system? It > seems that no one who can do it wants to so there must be a good reason.Q in order to be able to "give back" memory to the system we would have to switc

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

> 4. > >And, BTW, you can control it - see MAX_ constants at zend_alloc.h > > As I CLEARLY (as I think ...) described in > http://marc.theaimsgroup.com/?l=php-dev&m=98080647502573&w=2 > the mechanism of memory "deadlocks" is not based on the cache size > (it is small in fact), but in order of memo

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

OK, I'll try to summarize. > Because it will hurt performance, and gaining performance usually costs > much more that gaining memory (compare expense for doubling memory and > doubling performance). Most people in most cases are willing to trade > memory for performance - that's why caching exist

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

BM>> Yes, but it would be really nice if it was returned. Systems BM>> with 128MB or RAM run out quickly if there is a script ( like a BM>> long Phorum thread ) that takes a good chunk. Of course the BM>> argument can be made that the box needs more RAM but if the BM>> memory can be returned (ma

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

BM>> It is not a leak exactly but more of a greed. It seems to be a BM>> semi-intentional but not necessary thing. It seems that the way BM>> Zend/PHP is allocating memory is not allowing it to be returned BM>> to the system. Once PHP has some memory it will not let it go, BM>> but it will reus

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

hi, i'd disagree on this - imagine you have a webserver with reasonable load and 99.9% of php page requests use max 10mb ram. you have 1% that use 100mb ram. then it not a good idea to upgrade to 1g ram just for these 0.1% since each httpd process will hold 100mb ram after certain time (the 0.1%

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

AIL PROTECTED]> Sent: Monday, January 29, 2001 6:23 PM Subject: Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed. > Ok, so what are the benefits of not returning memory to the system? It > seems that no one who can do

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

;[EMAIL PROTECTED]> > > To: "Filip Sielimowicz" <[EMAIL PROTECTED]> > > Cc: "Brian Moon" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Monday, January 29, 2001 6:56 AM > > Subject: Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is

Fw: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

c: <[EMAIL PROTECTED]> > Sent: Monday, January 29, 2001 7:51 AM > Subject: Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed. > > > > On Mon, 29 Jan 2001, Filip Sielimowicz wrote: > > > > > > A quick fix would be to set your MaxRequestsPerChild to a low

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

> It is not a leak exactly but more of a greed. It seems to be a > semi-intentional but not necessary thing. It seems that the way Zend/PHP is > allocating memory is not allowing it to be returned to the system. Once PHP > has some memory it will not let it go, but it will reuse it. So, if a >

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

On Mon, 29 Jan 2001, Filip Sielimowicz wrote: > > A quick fix would be to set your MaxRequestsPerChild to a lower value. > > Have you ever tried to measure the time of killing and > starting httpd process ? You can see that with a bare human eye. Sure. But that isn't something that happens on a

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

> Yes, yes, I agree ! But this is the problem ! Unfortunatelly "memory > hungry script" happens from time to time and there's no chance to prevent > httpd processes from keeping memory (which is not used again in most > cases). Maybe it is not a problem for you, but it is for us. A quick fix woul

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

g better forums with PHP > -- > > > - Original Message - > From: "Rasmus Lerdorf" <[EMAIL PROTECTED]> > To: "Filip Sielimowicz" <[EMAIL PROTECTED]> > Cc: "Brian Moon" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent:

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

- - Original Message - From: "Rasmus Lerdorf" <[EMAIL PROTECTED]> To: "Brian Moon" <[EMAIL PROTECTED]> Cc: "Filip Sielimowicz" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, January 28, 2001 12:23 AM Subject: Re: [PHP-DEV]

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

PROTECTED]> Sent: Saturday, January 27, 2001 11:53 PM Subject: Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed. > > PS. Hey, guys from the php-dev. Don't you have anything > > to say ? Please do that ! > > Please do what? > > You should try to fi

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

an Moon" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, January 29, 2001 6:56 AM Subject: Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed. > > Yes, yes, I agree ! But this is the problem ! Unfortunatelly "memory > > hungry script" happens from ti

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

On Sat, 27 Jan 2001, Rasmus Lerdorf wrote: > > It is not a leak exactly but more of a greed. It seems to be a > > semi-intentional but not necessary thing. It seems that the way Zend/PHP is > > allocating memory is not allowing it to be returned to the system. Once PHP > > has some memory it w

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

> There is a thread that describes what happens and a discussion on how to > change Zend/PHP to not do this. Here is the link: > > http://marc.theaimsgroup.com/?l=php-dev&m=97923602322593&w=2 > > Now, being the 133t C hacker that I am NOT, I do not dare dive into this. > However, I did use the

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

> A quick fix would be to set your MaxRequestsPerChild to a lower value. Have you ever tried to measure the time of killing and starting httpd process ? You can see that with a bare human eye. -- PHP Development Mailing List To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

> PS. Hey, guys from the php-dev. Don't you have anything > to say ? Please do that ! Please do what? You should try to figure out what is leaking memory on you. None of my servers are leaking. -Rasmus -- PHP Development Mailing List To unsubscribe, e-mail: [EMAIL PROT

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

Dnia Wed, Jan 24, 2001 at 06:21:13PM -, [EMAIL PROTECTED] napisal: > From: [EMAIL PROTECTED] > Operating system: RH 7 > PHP version: 4.0.4 > PHP Bug Type: Performance problem > Bug description: Memory is not being freed. > > Hi guys, > > I do not have much information.

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

On 24 Jan 2001 [EMAIL PROTECTED] wrote: > From: [EMAIL PROTECTED] > Operating system: RH 7 > PHP version: 4.0.4 > PHP Bug Type: Performance problem > Bug description: Memory is not being freed. > > Hi guys, > > I do not have much information. I know that my Apache process

Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

n RedHat 6.2. - Jon - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 24, 2001 10:21 AM Subject: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed. From: [EMAIL PROTECTED] Operating system: RH 7 PHP version: 4.0.4 PHP B

[PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

From: [EMAIL PROTECTED] Operating system: RH 7 PHP version: 4.0.4 PHP Bug Type: Performance problem Bug description: Memory is not being freed. Hi guys, I do not have much information. I know that my Apache processes memory is growing by the minute. If I start a separate