Forum Discussion
Apr 27, 2005
Currently, there is no way to add HTTP Keep-alive support to the SOAP::Lite client libraries so the overhead of the SSL negotiation on each method call is unavoidable.
So, that leaves us with the total time being a function of the number of calls times the time each call takes
total_time = num_call * time_per_call
The time per call is fairly constant in the 500ms (+/- 200ms) range for the SOAP::Lite libraries so this should scale linearly with the number of calls made.
10 calls => 5s.
100 calls => 50s.
1000 calls => 8m 20s.
2000 calls => 16m 40s.
If you could post a logic flow of the application and which calls are made where, I can comment on whether there is a more optimal way to use the calls or whether alternate ways to get at the data would be more relevant.
-Joe