ID: 8931
Updated by: lobbin
Reported By: [EMAIL PROTECTED]
Old Status: Feedback
Status: Closed
Bug Type: Performance problem
Operating System: Windows 2000
PHP Version: 4.0.4pl1
New Comment:

No feedback. Closing.

Previous Comments:
------------------------------------------------------------------------

[2001-12-12 18:46:19] [EMAIL PROTECTED]

Could you try 4.1.0 see if it help?

------------------------------------------------------------------------

[2001-01-26 06:56:42] [EMAIL PROTECTED]

I've identified the problem as PHP leaking memory when it sees code that it doesn't 
like, eg. it leaks code when the script crashes with an error. I think that it leaks 
code even when it reads through functions and there is code in them which it does not 
recognise (that it will give an error, but ... because the function is not run, the 
script does not report an error, but memory is leaked anyway).

------------------------------------------------------------------------

[2001-01-26 06:38:40] [EMAIL PROTECTED]

The short version scored 7680 hits over 2 min, whereas the Object Oriented version 
scored around 1700 hits over 2 min running 4 threads.

Both scripts do the same thing, query to database, with same result, but the OO 
version seems to be 5 times slower, so I am classifying this bug as a performance 
problem.

------------------------------------------------------------------------

[2001-01-26 06:32:37] [EMAIL PROTECTED]

I wrote two scripts to compare the difference in performance between simple script and 
one written in OO with classes and required libraries. Both scripts accessed the SQL 
database using ADODB connection. I used Microsoft Web Application Stress Tool, which 
seems to be very useful.
The "simple" version yielded better performance in less CPU usage (and no memory 
leaking), whereas the OO version maxed out the CPU usage 100%, as well as slowly but 
surely leaking memory.
I tried using the unset() function in several places in the code, but this did not 
help much, as the script was still leaking memory during the tests.

Using unset() to unset the COM object helped a lot, as PHP did not seem able to free 
the memory by itself.

------------------------------------------------------------------------



Edit this bug report at http://bugs.php.net/?id=8931&edit=1


-- 
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