ID:               50410
 Comment by:       wzed dot php at gmail dot com
 Reported By:      procyonar at gmail dot com
 Status:           Open
 Bug Type:         cURL related
 Operating System: win32 only - Windows 7
 PHP Version:      5.2.11
 New Comment:

I'm also having this problem, with a freshly-extracted copy of
php-5.2.12-Win32.zip (php.ini edited to enable curl). In my case the CPU
spike lasts about 2 seconds (just running php.exe -v), but that's a
significant delay for someone who runs CLI scripts often.

It seems to only affect PHP 5.2.11 and 5.2.12, as I wasn't able to
reproduce it with 5.2.10 using the exact same php.ini file.

Confirmed on Windows 7 and XP.


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

[2009-12-08 13:25:20] procyonar at gmail dot com

Description:
------------
This is possibly the same problem as described in
http://bugs.php.net/bug.php?id=50406 .  PHP 5.2.11, vanilla distribution
from php.net, without any relevant php.ini changes, slows dows to a
crawl on Windows 7 Ultimate whenever php_curl.dll extension is enabled. 
It happens both in cli and in apache2 versions.

Just running "php -v" (version output) takes about 5-6 seconds when
curl is enabled (and a CPU usage spike).  With curl disabled, it is near
instantaneous, as expected.  I haven't tested whether curl actually
works.  A similar delay occurs on .php page load, etc.

WRT bug 50406, I believe curl initialization code, however complicated
it might be, is not supposed to take 5 seconds all by itself.  I
verified that in PHP 5.3.0 on Windows XP and PHP 5.2.11 on Gentoo Linux,
just to be certain, and in both cases there was no delay.

Reproduce code:
---------------
php -v

Expected result:
----------------
<1 s execution time

Actual result:
--------------
5-6 s execution time.  A similar delay occurs whenever ANY PHP script,
cli or apache2, is ran.


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


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

Reply via email to