This is another excellent tool to find out bottle neck. Fiddler and YSlow work on URL. Now suppose developer wants to check that which web services/ WCF services take how much response time, then SOAP UI helps.
| Scenario | Check Point | Analysis | Probable Resolution |
| 1 | Call all the Web services/ WCF servicing and capture the response time. Find out the services which has taken more than 1 sec | Find out the delay reason for the services. | If delay is due to DB call check the best practice is implemented for DB or not. If delay is due to specific server like CRM or CS call, check the configuration is proper or not. Check that proper data caching is implemented or not for relevant situation. if more than one instance created by application, make sure that instance should be garbage after use. Use Single ton or Factory methodology to maintain and create the instance of service. Use multi thread if services are taking more time. Create the new thread and call some related sub method/s parallel. Make sure all the Threading related best practice implemented to avoid deadlock.. |
| 2 | Network delay | Consider the scenario where IIS for application and IIS for Services are in different server. Call the service from the IIS server where the application is hosted and capture the response time. Now go to IIS server where the services are hosted and capture the response time for same service. Response times should be nearly identical for both the SOAP UI call. | If capture result has major response time different then problem at network side. Use the infrastructure tools which can give the exact information about where delay in network. |
No comments:
Post a Comment