At 04:59 PM 4/30/2001 -0500, Brian Moon wrote:
>This is the answer I had previously received.  IMHO, this sucks.  We don't
>do SQL queries on our production site.  It is all cached.  So, SQL is not
>the problem.  It is most likely because of the storage of large arrays or
>something of that nature.

Well maybe you should try and see what in your script is taking up lots of 

>I guess we will continue to use MaxRequestsPerChild until one day the people
>that wrote that memory allocation system get a clue.

They are very clue full. A program which uses X MB of memory is very likely 
to use X MB of memory again at a later time. For example, how does it help 
you if your 14 MB were shrunk back to 10 MB on each request. The next 
request would probably make it grow back to 14 MB.
There might be some memory management libraries that shrink the memory back 
but I doubt you can gain much from it especially as memory fragmentation 
can severally limit the amount of memory you can reclaim and because of the 
point I made before, it's probably just not worth it.

If you can find a case where you really think PHP is using much too much 
memory let me know and we can try and check together if there's a way to 
improve the situation.

PHP Development Mailing List <>
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