Clarity, Technology, and Solving Problems | PracticeThis.com
WP7 App with Key Windows Azure resources – Slides, Videos, How-To’s, and T-shooting – for quick consumption on the go.
Concise performance testing objectives document helps me staying focused, save time by creating shared vision among so many hands that are in it - biz analysts representing end users, dev teams, testers, IT folks and some more. To generate simple performance testing objectives document template I used stuff found here:
Here is what I have come with.
I used this section to set up front the perf requirements defined in app specification. This helps making sure expectations set with the biz analysts. For example:
Detect bottlenecks to be tuned.
This part I used to describe the parts of the system to pay most of my attention. Today's distributed systems involve very much components - IIS, SQL Server, Active Directory, MSMQ, and more. So here I try to stay focused on what is under my control, what can be measured and tuned. This part makes sure that application architectural characteristics have been taken into account. For example:
This part describes network environments and hardware high level characteristics to be tested. This part makes sure that sanity check has been done with regards to environments. Helps prioritizing on resources. For example:
This part should describe briefly what arch changes are to be made - for example moving from Web Services to WCF, AJAX to SilverLight. This helps prioritizing on metrics to be collected that would serve to support further architectural decisions.
This part describes exact hardware combinations to be tested.
This part actually describes what metrics to be collected to make sure enough data collected to make decisions on one but also help reduce amount of data that adds noise, Here is the simplest example:
Collect base line metrics (time taken) for all IIS servers - ASP.NET UI and Web Services.
This part describe known stuff - pitfalls or help materials - with regards to tested application. For example links to articles or other documentation.
part describe known stuff - pitfalls or help materials - with regards to tested application. For example links to articles or other documentation.
Final release - patterns & practices Performance Testing Guidance for Web Applications . It is the
Simple examination of IIS logs can reveal potential performance issues related to ASP.NET web applications,
Building ASP.NET web applications? Plan to serve thousands of users? Would you like to see how your application
How to anticipate or better off avoid performance related "surprises" during load and stress
PDD - Performance Driven Development presentation by Eran Kolbis made him my Super Hero! by Xurble Eran
Field experience proves - the earlier performance is tackled in development lifecycle the better results