I recently delivered this technical presentation – “Get Dirty with Diagnostics: Agile Performance Tuning at the Lowest Level” at HP’s 2013 Discover conference in Las Vegas. The presentation seemed quite well received, and showed a developing interest in performance testing and tuning within the Agile methodology.
The presentation has been split into 3 parts:
Learn how to get your hands dirty with Diagnostics and find out WHY your transactions times are breaking SLAs with a single user. This presentation provides a step-by-step walkthrough of how HP Diagnostics can be harnessed with agile to minimize time pressure, cost, and risk to .Net or Java application releases.
Avoid frantic, last minute efforts to debug that are often unfocused and costly. By using HP Diagnostics in an agile development and test cycle you can identify, fix, and retest code-level performance issues before they hurt the most.
This model has been successfully implemented on one of the largest SharePoint installations in the country, with over 8000 daily users. By providing code-level latency visibility to developers, performance issues are found and fixed quickly and accurately at Australia’s largest telecommunications provider.
Learn how to remove the performance issues from your next release go/no-go decision by getting your hands dirty with Diagnostics.