ID: 22880
Updated by: [EMAIL PROTECTED]
Reported By: project dot draco at gmx dot net
-Status: Open
+Status: Feedback
Bug Type: Performance problem
Operating System: win98//freebsd//any?
PHP Version: 4.3.2-RC
New Comment:
You need to provide us the same script to test this with.
Just testing on one machine does not give reliable results.
Previous Comments:
------------------------------------------------------------------------
[2003-04-05 09:39:31] project dot draco at gmx dot net
ok,ok
did some testing and found at least the following behaviour:
i kept track of includ_once times in my script and ran a couple of
times the same script, wich includes havily about 300 kB.
While 4.0.6 did this job with an avarage time of 0.4 ms per kB included
script, the 4.3.1 and 4.3.2 versions show an increasing amount of time
use to include_once the scripts.
Some values
sumsize avg 406 avg 432
0 0,55 0,47
16660 0,54 0,49
32859 3,92 3,65
57138 0,57 0,80
62766 0,46 0,74
83208 0,46 0,77
106302 0,44 0,69
114039 0,56 0,93
119067 0,57 1,17
129474 0,62 1,08
150891 0,90 1,70
161932 1,46 1,74
167775 0,43 0,83
182655 0,42 1,06
209909 0,47 1,63
246752 0,49 1,51
269711 0,42 1,61
330045 0,48 1,85
346306 0,41 1,64
The three bigger values (3.92,0.90,1.46 at the avg406 col) are scripts
that do initial executions and db-queries, so we ommit them.
the rest is simple classdefs, no initializing done.
As you can see, the 432 avg times increase with increasing filesize
(the sizes are summed up so 346306 is the full scriptsize that is run)
Can you read anything helpful out of this posting???
ps Testing was done on win98/php-cgi/apache 1.3.20 systemenvironment.
gruss
mir
------------------------------------------------------------------------
[2003-03-31 02:13:08] [EMAIL PROTECTED]
Still waiting for the feedback of more detailed information.
------------------------------------------------------------------------
[2003-03-30 05:10:09] project dot draco at gmx dot net
Gave it a try.
Didn't work, sorry. As slow as before...
So now im going to make some testings to find out, where the
performance loss originates from.
I already localized some strange side effects, wich point to the
conclusion, that it is in fact something with the memorymanagment.
The same script, executed as standalone is much faster, than executed
within a huge script.
Ill be back with some more accurate bug-report soon.
so long
mir
------------------------------------------------------------------------
[2003-03-25 14:48:32] [EMAIL PROTECTED]
Please try using this CVS snapshot:
http://snaps.php.net/php4-STABLE-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-STABLE-latest.zip
There was a performance problem for file() and file_get_contents() on
systems without memory mapping support; this has been fixed in the
stable snapshots.
Please give it a try.
------------------------------------------------------------------------
[2003-03-25 12:43:16] project dot draco at gmx dot net
I switched from php 4.0.6 to 4.3.1 lately. I run php as cgi on an
win98-apache 1.3.20-php-mysql system.
I think i missed all versions in between, but now i realize a
performance loss of about 50% (execution time nearly doubled without
ANY code changed, simply giving Apache a different cgi)
I was able to catch up partly by tuning the php.ini (i never did this
before!) but still expirience serious performance loss.
This mostly seems to take place on database and filesystem operations,
but i'm not sure of this.
Could someone measure this out?
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=22880&edit=1
