RE: [PHP-DEV] Forced garbage collection
| From: | Stanislav Malyshev | Date: | Thu, 29 Jun 2000 18:41:27 +0000 |
| Subject: | RE: [PHP-DEV] Forced garbage collection | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-22885@lists.php.net to get a copy of this message | ||
PK>> Ok. I know it obvious that I need to retest this problem on 4.0.1.
PK>> However, I take it from both Andi and Rasmus' response that garbage
PK>> collection should definately have occured by the end of the script. Also,
PK>> there is presumably no way to force garbage collection at the end of a
PK>> script becuase it should have happened anyway.
PK>>
PK>> I seem to recall that there was some way or forcing apache daemons to
PK>> recycle. Does anyone recall how to do this? Or, if it is even possible?
You can set low MaxRequestsPerChild. But it'd mean performance hit.
Also, do you have stuff like persistent connections, etc.? The problem
here could be that if you have allocated block of 70M and then another 16
bytes, and then freed 70M - it'll still be around your heap until you free
16 bytes on top of it. That's how malloc works on most systems.
--
Stanislav Malyshev stas@zend.com
+972-3-6139665