Using localhost does not mean that DNS is not used. It is necessary to resolve
localhost to an IP
address, and the name resolution configuration may be such that DNS is used before the
hosts file.
On Windows, the situation is worse, in that NetBIOS broadcast and WINS lookup can be
configured to
have priority over hosts, lmhosts and DNS.
Anyway, if it takes 375 ms to create a Call object, you have other problems. Almost
no code is
executed to do this. All the real work is done as part of Call#invoke.
Your 800-1000 ms is *much* slower than I experience with the AddressBook sample, and I
run NT and
Win2k on a 400 MHz K6-3. My software is IIS and JRun, though, which I found
significantly faster
than Apache and Tomcat (or Tomcat standalone) for this purpose.
Scott Nichol
----- Original Message -----
From: "sac vish" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 12, 2001 14:06
Subject: RE: Performance issues with Apache SOAP
> Hi Shaun,
> I am using 'localhost', so I guess, DNS and routing should not come into
> picture.
>
> I am not sure of reusing the object, as Apache SOAP does not provide
> reference to remote object, I believe every time it instantiates the new
> remote object. Does it provide objet pooling?
>
> You have mentioned about HTTP enhancements, do I need to some setting to
> leverage these things? Since keep-alive is currently not supported how the
> HTTP connection gets reused?
>
> Thanks
> Sac
>
>
> >From: [EMAIL PROTECTED]
> >Reply-To: [EMAIL PROTECTED]
> >To: [EMAIL PROTECTED]
> >Subject: RE: Performance issues with Apache SOAP
> >Date: Tue, 12 Jun 2001 10:14:45 +0300
> >
> >Hi Sac,
> >
> >Are you using localhost ? Remember that SOAP is a network based technology
> >so check that things like any DNS lookups and call routing are not slowing
> >things down. Also remember that you should be looking to re-use objects
> >where possible especially ones that have a high initialisation overhead.
> >I'm not sure at this time about 2.1/2.2's use of HTTP 1.1 and re-usable
> >HTTP
> >connections. If you are sending multiple soap messages to the same
> >endpoint
> >look at using this enhancement to HTTP.
> >
> >Regards,
> >
> >Shaun O'Hagan
> >London UK.
> >
> >-----Original Message-----
> >From: ext sac vish [mailto:[EMAIL PROTECTED]]
> >Sent: Tuesday, June 12, 2001 12:46 AM
> >To: [EMAIL PROTECTED]
> >Subject: Performance issues with Apache SOAP
> >
> >
> >Hi ALL,
> >I was curious to know whether anybody has done bench marking on Apache SOAP
> >2.1/2.2? I found it to be very slow,it takes around 800-1000ms per SOAP
> >call. I have not debugged the code but it seems just to create the 'Call'
> >object it takes 375ms. Could somebody tell me why it takes that long??
> >Is there any possiblity to optimize it, if only HTTP transport is needed?
> >
> >Thanks
> >Sac
> >_________________________________________________________________
> >Get your FREE download of MSN Explorer at http://explorer.msn.com
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
