Hi,
While using a simple client to test SOAP performance, I noticed an
exponential increase in the unmarshalling process time for my RPC return
values. I remember hearing that creating Document objects can be a very
slow operation, related to the String size being processed. The
return object, in this case, is itself a String of XML obtained from a
dbXML query.
1) Does the Document builder get confused by this additional
XML inside the Envelope (I'm guessing no)?
2) Is there a faster/better way to acheive this?
3) Are there any considerations for allowing for pluggable unmarshalling
mechanisms, i.e. SAX-based?
I was impressed by the low overhead of smaller return
values but for our purposes, the exponential increase is unacceptable.
Here are some times ( in ms) and responses (in lines of xml):
Response length SOAP NON-SOAP
2023 3987 1246
1072 2636 1063
495 1293 796
80 628 549
I used the same query in both runs, the same 1.3 VM in classic mode and
timed the point of request to the point of
response ( so no set-up or VM ramp-up delays are included ).
I noticed a similar message posted today June 7 by Tom Meyers with
similar
complaints. I was unable to successfully implement this work around- the
result was a vague SOAP:ENV Server.Exception fault originating in the
Serializer.
Thanks
Ian Schneider : >(
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
