> From: Aleksander Slominski [mailto:[EMAIL PROTECTED] [...] > 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.
I reran the test and dumped the network traffic through ethereal. According to that test 480 ms is spent in axis' code and the parser for a large reply (not 650 as i said before), and 150 ms for a small reply (the requests are always small). I havent found M, but lets assume it's small and constant. I use the "default" xerces parser. It uses 170 ms to process the large reply (using the SAX parser with an "empty" content handler). This means that axis uses about 300 ms to process the large reply. This includes deserializing about 1000 objects (mostly Dates and Strings (many are null)) and primitive values. Maybe not so bad after all? -- Regards André Risnes
