Re: [ZEND-ENGINE-CVS] cvs: Zend / zend.czend.hzend_config.nw.h
| From: | Zeev Suraski | Date: | Tue, 07 Jan 2003 22:38:00 +0000 |
| Subject: | Re: [ZEND-ENGINE-CVS] cvs: Zend / zend.czend.hzend_config.nw.h | ||
| References: | 1 | Groups: | php.zend-engine.cvs |
| Request: | Send a blank email to php-zend-engine-cvs+get-765@lists.php.net to get a copy of this message | ||
At 11:45 07/01/2003, Ananth Kesari wrote:
Yes. On NetWare there is no concept of processes. Everything is thread centric. There could be a thread group though in which many threads can be grouped. But every "process" that is spawned is treated as thread by NetWare. Also, there is no concept of something like "garbage collector" on NetWare. Also, we cannot indicate to NetWare when to clean up the resources, we have to explicity clean them up. But why is the memory leak intentional in PHP? Is it for speed?Well, I would say that convenience was a motivation as well. There are some things that are just too much of a headache to track, and in both Windows and UNIX, there's no point tracking them. The fact it also ends up being faster is also an issue, a minor one.
But in any case, we are freeing only on destruction and so the operational speed does not get affected due to this. So, we can do the free's while destruction right? Am I correct in my understanding?In CGI's, explicitly freeing will actually affect the overall performance. But I doubt it will be noticeable. Zeev