#41943 [Opn->Fbk]: Soap Call causes CPU to go 100%
| From: | tony2001@php.net | Date: | Mon, 09 Jul 2007 19:45:35 +0000 |
| Subject: | #41943 [Opn->Fbk]: Soap Call causes CPU to go 100% | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-114818@lists.php.net to get a copy of this message | ||
ID: 41943
Updated by: tony2001@php.net
Reported By: simon at connexon dot com
-Status: Open
+Status: Feedback
Bug Type: Performance problem
Operating System: Windows Server 2003
PHP Version: 5.2.3
New Comment:
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
Previous Comments:
------------------------------------------------------------------------
[2007-07-09 19:39:46] simon at connexon dot com
Description:
------------
We've been using soap for a while now and noticed that when we send a
soap request and it waits for a response, PHP goes in a sort of loop and
takes CPU load. Our average waiting time is 4 seconds.
A soap call once in a while is ok, because it doesn't take too much CPU
overall. But we noticed that the more we grow, the more CPU it takes, to
a point where we reach often 100% CPU if we do a loop of soap calls.
(All that caused by the waiting time of the soap call!!!).
Reproduce code:
---------------
x
Expected result:
----------------
Would it be possible that PHP goes into an idle mode when it waits for
a soap response instead of taking all the CPU ressources?
Actual result:
--------------
CPU goes crazy when we do too many soap calls in a row (we can do
maximum of 4 soap calls at once, else it would overload the server).
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=41943&edit=1