Andi's statement is correct.  I believed that but felt something else was
wrong.  Andi gave me the benefit of the doubt (yeah Andi!) and took a close
look at the code.

I asked him what he changed and he said:

"The memory manager did some memory block caching which was causing very bad
fragmentation. I fixed it so that it'll minimize memory fragmentation in
between requests."

So, good for PHP!

Brian Moon
------------------------------------------
dealnews.com, Inc.
Makers of dealnews & dealmac
http://dealnews.com/ | http://dealmac.com/


----- Original Message -----
From: "Brian Foddy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, June 22, 2001 8:20 AM
Subject: Re: [PHP-DEV] Bug #8889 Updated: Memory is not being freed.


> Not that I believed anything serious was wrong, but can you tell
> me specifically what was "fixed".  Is there any change in Andi's
> statement (which is always what I've understood)?
>
> Brian
>
> [EMAIL PROTECTED] wrote:
> >
> > ID: 8889
> > Updated by: brianlmoon
> > Reported By: [EMAIL PROTECTED]
> > Status: Closed
> > Bug Type: Performance problem
> > Operating system:
> > PHP Version: 4.0.4
> > Assigned To:
> > Comments:
> >
> > This is all fixed in 4.0.6.
> >
> > Previous Comments:
>
> --------------------------------------------------------------------------
-
> >
> > [2001-05-01 03:01:29] [EMAIL PROTECTED]
> > The main problem is that once the system's standard C library allocates
heap space (with the sbrk() system call) it will never return that memory to
the system.
> > PHP can't solve this problem. If you do find certain things in the
future which take up much more memory than they should please open a new bug
report and we will check into it.
> >
>
> --------------------------------------------------------------------------
-
> >
> > [2001-04-30 14:31:27] [EMAIL PROTECTED]
> > I am talking about nearly endless amounts.  I saw Apache processes with
as much as 14MB of memory in use.
> >
> > Brian.
> >
>
> --------------------------------------------------------------------------
-
> >
> > [2001-04-29 19:59:56] [EMAIL PROTECTED]
> > What kind of sizes are we talking about here?  the Zend memory manager
holds a memory cache, but we're talking at around 1MB per process max.
> >
>
> --------------------------------------------------------------------------
-
> >
> > [2001-01-26 18:45:45] [EMAIL PROTECTED]
> > Ok, this is just like what is described in
http://marc.theaimsgroup.com/?l=php-dev&m=97923602322593&w=2 which contains
a hacked up solution.  It looks like it should be able to turn into a usable
end solution.
> >
>
> --------------------------------------------------------------------------
-
> >
> > [2001-01-24 13:21:13] [EMAIL PROTECTED]
> > 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 server on another port and
serve only static pages and files through it, those process do not grow.
> >
> > I have tried what I remembered of gdb but have not come up with
anything.  I know I need to attach to a process and it seems I can `gdb
{pid}` but that gives me nothing.  How can I get some info for you guys?  I
do have --enable-debug.
> >
> > thanks,
> >
> > Brian.
> > Phorum.org
> >
>
> --------------------------------------------------------------------------
-
> >
> > The remainder of the comments for this report are too long.  To view the
rest of the comments, please view the bug report online.
> >
> > ATTENTION! Do NOT reply to this email!
> > To reply, use the web interface found at
http://bugs.php.net/?id=8889&edit=2
> >
> > --
> > PHP Development Mailing List <http://www.php.net/>
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
>


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to