Your performance matches what I've seen on Win2K with sun 1.3.1, 1.3.1_01 and ibm's lastest 1.3.0. I don't believe you're going to get the overhead down from there on a Win2K box until we jump to the next architecture of apache soap.
I've seen a wide range of times on Linux when I timed with different JVMs. However, I don't recall seeing times drop down to the level you're reporting. What JVM/OS/version are you running on Linux? Heitzso Anthony LaMarca wrote: >Ack! I'm stuck, and hoping one you wonderful people can bail me out. > >I'm running soap 2.2 and I'm getting terrible performance running the server on >a windows 2000 box. I've run soap on both tomcat and jetty and I get the same >thing: about 200ms for a roundtrip call. My service is trivial, returns a fixed >string. Its not startup costs; if I do the calls over and over again they're >all about 200ms. If I move the server over to a (much slower) linux box, the >call time drops to around 20ms. All of the machines are connected to the same >100MB/s hub, so there shouldn't be any network latency issues. The client is >also a win2k box. > >Any idea why win2k would be screwed up but linux (redhat 7.2) would be ok? >My only thought is that our dns setup might be wacky, our sys-admin is kind of >clueless. But I'm invoking the services with ip addresses rather than >hostnames, so I'm not sure dns has anything to do with it. > >how can I fix this? > >Thank you thank you thank you!!!!!!! > >-Anthony > >__________________________________________________ >Do You Yahoo!? >Make a great connection at Yahoo! Personals. >http://personals.yahoo.com >
