I'm running a workflow application from a Web application.
The workflow does not scale well.
When simultanious requests are made the results are:
- 1 user. Response time around 10 seconds.
- 2 users. Response time around 15 seconds.
- 3 users. The Workflow Runtime appears to get stuck in a loop and the w3wp.exe process hogs all server resources. The only way to free the resources is to restart IIS or the server.
Has anyone encountered similar problems or got any suggestions.
Regards
Parlster
Multiple requests clogs w3wp.exe
Jeffrey Litch
Hi Parlster,
To get performance from an ASP.NET hosted workflow you'll need to use the Manual Thread Sheduler in WF. In the current public build WF Beta 2.2 this sheduler service does not support delay timeouts. See this post for some detail on this.
Regards,
Paul
XBTester
Could you outline your scenario and how are workflows being hosted in w3wp.exe. Also what version of WF are you working on
ReneL
Paul,
Thank you for your response.
I believe you have hit the nail on the head.
I was using WWF to run an insurance rating guide. Performance for a single run was poor (compared to a class based solution) and under stress (more than 2 simultaneous requests!) the application failed. Observation would suggest the timeout problem you identified.
I've gone back to a class based solution but will return to WWF when the fix has been implemented.
Do you have any opinion on the use of WWF for such intensive procedures
Regards
Parlster
Morgan Cheng
Vishal,
Thank you for your interest and sorry for the slow reply.
I was using V2 beta.
The application was an ASP.NET application running in IIS.
I believe Paul's post has identified the problem. The Workflow I was using was very intensive (an insurance rating guide) so I believe timeouts were the issue.
Regards