Slow web service call

Slow web service call

Post by UXVlbnRpbi » Sat, 12 Feb 2005 19:49:15


Hello,

Here is my problem; I have 5 calls to 2 diferrents web services inside an
orchestration. I debatch the file inside the orch and do a Loop for all the
messages.
For each message I call the web services, and it is very very slow!
It seems that for each message, it create an instance of the web service ...
So for each message, it takes 2-3 secondes per web service ...

You can imagine the lack of time for 200 messages ...

Does anyone know if there is a way to say that we want to have only one
instance (object) of the web service for the whole messages?

Thanks a lot
 
 
 

Slow web service call

Post by QWxhbiBTbW » Wed, 16 Feb 2005 19:07:03

Hi,

Debatching large messages in the orchestration is sometimes slow, one option
could be to debtch in the puipeline, and create one orchestration instance
per debatched message (if this is possible in your scenario).

There'a a good blog post on this here:
http://www.yqcomputer.com/

Another option to speed things up may be to use the parallel acions shape
when calling several web services.

Regards,

Alan

 
 
 

Slow web service call

Post by UXVlbnRpbi » Wed, 16 Feb 2005 19:17:02

Hi,

In fact in a first time I was debatching in the pipeline, but that doesn't
allow me to delivery the messages in the order, that's why I need to debatch
in the orchestration and loop for all the messages (in the order).
But by doing that, the web service calls are not done in the same time, so I
lose precious seconds for each message ...
That's why I would like to use the same instance of the web service for the
whole messages in the orchestration .... (I managed to do this, but by using
a C# class calling the web service that I use by a var in my orchestration...)

I'm really searching why this web services are so slow ... (in fact the
instanciation ...), is it a BizTalk problem ....? Or am I missing something?

Tanks a lot for your help
 
 
 

Slow web service call

Post by Matt Milne » Thu, 17 Feb 2005 12:53:08

Part of the issue is that each call to the web service involves 1)
publishing your request to the message box, 2) the send adapter getting this
message and actually making the SOAP call, then 3) placing the response back
in the message box, where it can be 4) picked up by the orchestration. Take
a look at this peformance characteristics whitepaper for information on how
you can tune your server for different adapters:

http://www.yqcomputer.com/

Matt


>> Hi, >> >> In fact in a first time I was debatching in the pipeline, but that doesn't >> allow me to delivery the messages in the order, that's why I need to >> debatch >> in the orchestration and loop for all the messages (in the order). >> But by doing that, the web service calls are not done in the same time, so >> I >> lose precious seconds for each message ... >> That's why I would like to use the same instance of the web service for >> the >> whole messages in the orchestration .... (I managed to do this, but by >> using >> a C# class calling the web service that I use by a var in my >> orchestration...) >> >> I'm really searching why this web services are so slow ... (in fact the >> instanciation ...), is it a BizTalk problem ....? Or am I missing >> something? >> >> Tanks a lot for your help >>
>> >>> Hi, >>> >>> Debatching large messages in the orchestration is sometimes slow, one >>> option >>> could be to debtch in the puipeline, and create one orchestration >>> instance >>> per debatched message (if this is possible in your scenario). >>> >>> There'a a good blog post on this here: >>> http://www.yqcomputer.com/ >>> >>> Another option to speed things up may be to use the parallel acions shape >>> when calling several web services. >>> >>> Regards, >>> >>> Alan >>> >>> >>>