RE: Poor performance in parsing kSOAP response. Ideas?

Sebastien,

I'm testing on a 1.6Ghz P4, 512MB RAM, XP Pro running Eclipse (for
development) and the 1.0.4 Wireless toolkit from Sun. In fact, nearly
all the kxml parsing seems to take a really long time to come back. For
example, even a short uncomplicated response (with a couple of fields)
takes 5 seconds, whereas just using "indexOf" to rip the results out (no
parsing) takes 2 seconds. As I stated before, I have not turned on any
of the "performance emulation" features of the toolkit (e.g. VM%,
network latency/bandwidth etc.)

Jonathan

-----Original Message-----
From: [email protected]
[mailto:[email protected]] 
Sent: Tuesday, February 18, 2003 12:48 AM
To: [email protected]
Subject: Re: Ksoap: Poor performance in parsing kSOAP response. Ideas?


Hi,

On what kind of configuration is your stuff running ?
What about the other Java code running on your device ? 
Isn't it a problem with the JVM ?

Regards,
Sebastien.


"Jonathan Trevor" <[email protected]>
Sent by: 
[email protected]
2003-02-14 02:40
Please respond to ksoap

 
        To:     <[email protected]>
        cc:     (bcc: Sebastien Petrucci/LEU/COMP/PHILIPS)
        Subject:        Ksoap:  Poor performance in parsing kSOAP
response. Ideas?
        Classification: 



Hi,

I'm using kSOAP to call .NET web services. I managed to get both the
.NET services and the kSOAP calls to work correctly after reading a few
very useful messages here. 

However, Im seeing really really poor performance from the kxml parser
running the the J2ME wireless toolkit emulator (no "slow down" options
used). I added some timing code around the http transport and the parser
is taking over 50 seconds for an array of 60 results of this "GetInfo"
response:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="http://blah.blah.com/"
xmlns:types="http://blah.blah.com/encodedTypes"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <GetInfoResponse>
      <GetInfoResult href="#id1" />
    </GetInfoResponse>
    <soapenc:Array id="id1" soapenc:arrayType="types:Details[2]">
      <Item href="#id2" />
      <Item href="#id3" />
    </soapenc:Array>
    <types:Details id="id2" xsi:type="types:Details">
      <ID xsi:type="xsd:int">int</ID>
      <Target xsi:type="xsd:string">string</Target>
      <Target2 xsi:type="xsd:string">string</Target2>
      <Target3 xsi:type="xsd:string">string</Target3>
      <Hkey xsi:type="xsd:long">long</Hkey>
    </types:Details>
    <types:Details id="id3" xsi:type="types:Details">
      <ID xsi:type="xsd:int">int</ID>
      <Target xsi:type="xsd:string">string</Target>
      <Target2 xsi:type="xsd:string">string</Target2>
      <Target3 xsi:type="xsd:string">string</Target3>
      <Hkey xsi:type="xsd:long">long</Hkey>
    </types:Details>
  </soap:Body>
</soap:Envelope>

That's unusably slow.

In addition, I am working from the source distribution which I have
modified slightly to handle cookies in the http transport class, as I
need it for session tracking, and added the support for dates and base64
byte arrays.

Any thoughts on this performance? Is it what I should expect? I guess if
it is then I'm going to need to write some horrible http proxy coding
techniques and avoid soap entirely - which is a great shame!

Thanks
Jonathan

_______________________________________________
Ksoap mailing list
[email protected] http://www.enhydra.org/mailman/listinfo.cgi/ksoap



_______________________________________________
Ksoap mailing list
[email protected] http://www.enhydra.org/mailman/listinfo.cgi/ksoap