1. Performance is activity which development team should start parallel. During the development phase, performance should be measure using the mention tools and store the result into source control for future comparison.
2. Design and Architecture should be sign off and any small changes should be documented and validate for performance impact.
3. After every release of milestone –
a. Fiddler and YSLow should be run and analysis for the performance. Store the result into source control for future comparison.
b. Capture result using SOAP UI for all the service and resolve if any conflict.
c. Run ANTS or other profiler and generate report for all the methods. If any issues/bottleneck, resolve immediately.
d. BPA tools must be executed on hosting environment and resolve if any conflict.
e. Capture trace using SQL profiler and send report to DBA for Analysis. The best way is to run load runner and capture the trace file.
f. Capture report for CPU and memory utilization using PAL.
g. Effective Code review should be done. Use “Code Analysis” tool for best practice for coding. Use “Generate Dependency Graph” to identify the complexity.
h. Collect response from UAT(User Experience Team) and work on improvement areas.
4. During the architecture phase
a. Decide how to implement Caching, Exception handling ,Validation and Transactions..
b. Use factory or abstract factory design pattern to create the object of WCF/ WEB Services.
c. Define best practice for integration to other system with performance check points.
5. Develop application in the production type environment. If not possible than at least after each milestone - host the application in production type environment; capture the result using YSLOW/fiddler, compare result with the one which development team has capture in development environment.
6. Implement security (authorization and authentication) as per the client recommendation in first release so any performance related issues popup can be solve before actual development start.
7. After doing any IIS setting changes, require to check concurrency.
8. Involved UAT (User Experience Team) for better user experience.
No comments:
Post a Comment