The problem is probably not in the SOAP, but probably in whatever you implemented within the web service backend to do the "fetch." Whatever SOAP library you're using for PHP, they can all execute in 100ms or less. You can try to take the classes implementing your service and instrument them in a simple command line script and time the responses and observe the system. Regards, Al On Thu, 2007-10-18 at 21:58 +0200, Claus Jørgensen wrote: > Hey > > SOAP is heavy operations as XML is not the most lightweight format you can > find for data transfer. > You should ask yourself why you are requireing to do updates each 3 seconds, > and think of ways to persist the objects/data on your machine. > > Perhaps look at APC, if you can cache some of the data. > Else you will probably have to use a more lightweight protocol, such as > direct TCP/IP rather than XML/SOAP. > > 2007/10/18, Javed Chauhan <little_heartly@yahoo.co.in>: > > > > > > Hello, > > We have developed one site and in this we are calling methods. > > Basically this is auction site. > > > > So it is calling every 3 seconds. > > > > When we call auction fetch methods ,cpu reaches 90% usage thats why site > > down at that time. > > > > We are making soap object every time and calling methods every time. > > So if any of you know how to control them or any other methods by which we > > can solve our > > problem. > > > > Site url is tjc.tv > > > > > > Thanks, > > Javed > > > > > > > > -- > > View this message in context: > > http://www.nabble.com/cpu-usage-reaches-90--while-calling-method-tf4646658.html#a13273521 > > Sent from the Php - Soap mailing list archive at Nabble.com. > > > > -- > > PHP Soap Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > -- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php