Andre Risnes wrote:
Thanks Yuval for your suggestion to use JProfiler.
I ran my test in it, an although I don't have a lot of experience using profilers, I believe I've found that only about 25% of the time used was network overhead, and about 70% was XML processing.
This means that the axis client uses about 650 ms to process a
~120 KB SOAP reply, on a 2.4 GHz Intel CPU. The message is long
but not complex (a table with 100 rows with two complex types
per row). Does this sound reasonable to you guys?
that depends on what you expect :)
what i would do: write a small test program and see how long does it take for the XML parser you use to parse this ~120 KB SOAP reply (N), how long does it take to write XML for SOAP request (is it small?) (M), and then compare how long does it take for AXIS to process round-trip very small SOAP request/reply (K) and you will know overhead.
if what actual timing you get is much bigger than N+M+K than something that is going on inside engine needs fixing. in such case prepare a test case and describe issue in JIRA: http://ws.apache.org/axis/bugs.html
you may look on existing issues to learn how they were identified and fixed such as:
http://issues.apache.org/jira/browse/AXIS-1323
also try different XML parsers ... http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/XMLParsers
HTH.
alek
-- The best way to predict the future is to invent it - Alan Kay
