In researching problems with SOAP::Lite, I hit upon this PDF (Google HTML version).
I was quite surprised to see how much slower SOAP::Lite was compared to other implementations - it's latency is 35 times that of the JavaRMI implementation, with actual requests being about 100 times slower (in the examples they used).
Not knowing much about TCP, I'm not exactly sure what the problem is as described, but one comment stands out:
"SOAP::Lite automatically serializes associative arrays where the same object may be referenced more than once. My guess is that while this is very convenient, it has a large impact on performance."
Is anyone else aware of these issues? How easy would the problems be to address? We've decided to move away from Perl on the server end of transactions and will wait and see what happens. If you use SOAP, what approach have you taken?
Thoughts anyone?
cLive ;-)
Edit: OK, I misread it, but I'm still interested in whether anyone's been looking at speeding up the module :)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: SOAP::Lite - worst SOAP implementation?
by perrin (Chancellor) on Apr 12, 2005 at 19:04 UTC | |
by cLive ;-) (Prior) on Apr 12, 2005 at 19:13 UTC | |
by bluto (Curate) on Apr 12, 2005 at 20:50 UTC | |
|
Re: SOAP::Lite - worst SOAP implementation?
by samtregar (Abbot) on Apr 12, 2005 at 20:41 UTC |