Re: SOAP performance data and open benchmarks

Leo is correct, and I just want to add that you will want to make sure your network transmissions are actually a bottleneck before embarking on a project to improve them -- you know, premature optimization and all that. For example, if you're feeding XML messages into a business process involving workflow with humans in the loop -- for example, a document must get signature approval before it can proceed in the workflow, and that approval might take days -- then obviously a few extra seconds of network transmission time for the XML messages won't be noticeable.

--steve

> -----Original Message-----
> From: Leo Golubovsky [mailto:[email protected]]
> Sent: Friday, October 18, 2002 9:13 AM
> To: [email protected]
> Subject: Re: [SOAP] SOAP performance data and open benchmarks
> 
> 
> In reality this computation gets a bit more complex with 
> external clients.
> First you don't always control external connections.  Second 
> think how XML
> request gets accepted on processing side.  In most cases you 
> have a router
> and webServer or reverse proxy in DMZ first.  Then it 
> transfers data to your
> XML server where it finally gets processed.
> 
> So you need to account for all these hops.
> 
> Leo Golubovsky
> [email protected]
> 
> -----Original Message-----
> From: Discussion of implementing SOAP applications today
> [mailto:[email protected]]On Behalf Of Neelakantan 
> Lakshminarayan
> Sent: Friday, October 18, 2002 8:02 AM
> To: [email protected]
> Subject: Re: [SOAP] SOAP performance data and open benchmarks
> 
> 
> > We found in our testing that XML messages, especially big business
> > transactions, have excellent size reduction ratios.  You need to
> compromise
> > speed of compression/decompression against speed of data transfer.
> > The other issue is that you will need to add decompression 
> and compression
> > filters yourself into standard SOAP packages that don't 
> have this feature
> > out of the box.  And all your clients must follow this protocol.
> Internally
> > this is easy to accomplish.  Externally is a different story.
> >
> > Leo Golubovsky
> > [email protected]
> >
> 
> Is there any statistics out there which provides guidance on 
> the speed of
> compression versus speed of data transfer? This would vary 
> for the modes of
> compression, of course.
> As a client or server how do I decide if this particular 
> reques/response
> should be compressed or not? Is it practical to make this 
> judgement call for
> every request/response?
> 
> I'm curious how people handle this.
> 
> Thanks!
> Neela
> 
> You can read messages from the SOAP archive, unsubscribe from SOAP, or
> subscribe to other
> DevelopMentor lists at http://discuss.develop.com.
> 
> You can read messages from the SOAP archive, unsubscribe from 
> SOAP, or subscribe to other
> DevelopMentor lists at http://discuss.develop.com.
> 

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.