Thanks for the reply,
I guess you are right the same is happening with me, the initial request takes considerably more time and then the following requests take lesser and more consistent time to process requests. What I've read about biztalk, why it should be doing this is that, when the process (BizTalk assembly containing the process) isn't utilized for a specified amount of time, it is unloaded from the memory, hence when you call it after that it takes time to process the request, but after that it loads that assembly in the memory for a specific period of time and calls made to it during that time would process faster and more consistently.
But this creates the problem of those initial calls (when the biztalk assembly is not loaded in the memory) would take more time, thats not a desirable option in most cases, so my question now is how can we avoid that initial lag in time that happens because of the assembly being not already loaded in the memory?
Also, is their a way we can set the time in biztalk to keep the assembly in memory, if the assembly isn't utilized (called)? and what would be the impacts of increasing that time?
Regards,
Sajid.