1 / 22

A Day in the Life of an Application Performance Engineer Keith Lyon - Shunra Software keith.lyon@shunra.com

A Day in the Life of an Application Performance Engineer Keith Lyon - Shunra Software keith.lyon@shunra.com. Introduction. Who am I? What’s my background? How did I get introduced to Shunra?. Performance Testing Ecosystem Overview. A day in the life…. My application is so slow…

baina
Download Presentation

A Day in the Life of an Application Performance Engineer Keith Lyon - Shunra Software keith.lyon@shunra.com

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Day in the Life of an Application Performance EngineerKeith Lyon - Shunra Software keith.lyon@shunra.com

  2. Introduction • Who am I? • What’s my background? • How did I get introduced to Shunra?

  3. Performance Testing Ecosystem Overview

  4. A day in the life… • My application is so slow… • We take breaks between button clicks… • What do you mean, did we “performance test”? • Non-functional requirements? • Network \ application profiling?

  5. Why do we performance test? • Determine speed or effectiveness of a computer, network, software program or device. • Quantitative tests done in a lab, such as: • measuring the response time or the; • number of MIPS (millions of instructions per second) at which a system functions. • Qualitative attributes such as: • reliability, scalability and interoperability may also be evaluated.

  6. What are “non-functional” requirements? • A requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. For example: • Transactions per second; • CPU Utilization; • Memory Utilization; • Maximum Throughput.

  7. Describe the “Performance” of a system • Response Time: Typically defined as the time taken to complete a single business transaction. It is usually expressed in seconds. • Throughput: Can be defined as the total number of business transactions completed by the application in unit time (per second or per hour). • Resource Utilization: Different resources factored in, such as processor, disk (i/o controller), memory etc.

  8. Performance Test Plan: What To Test • 80/20 Rule • Classify transactions • Critical business processes

  9. Performance Test Environment • Capacity • Scalability • Node Deployment

  10. Performance Test: Data Preparation • Initial Data Setup • Ongoing Data Retention • Test Data

  11. Value In Reporting

  12. Performance Test: Best Practices • Reusable Automated Core Scripts; • Database backups after crucial runs; • Designing scenarios to achieve right mix of transactions; • Do not tune, if you don't have to.

  13. Real Life Example: The Project… • Custom Developed Application; • Hosted by Third Party; • Rolling Out to 250 International Sites; • Time to Performance Test = 1 Month.

  14. Network Model

  15. Shunra Suite of Products and Hardware

  16. Shunra Proprietary

  17. Shunra Professional Services

  18. Shunra Professional Services

  19. Shunra VE Desktop for HP Loadrunner

  20. TRY and FLYEnter to Win Free Round-trip Airfare to HPSU BarcelonaTest Drive Shunra for HP™ - 30 Day TrialContact James Newton @ 267-519-5104 or james.newton@shunra.comWinner announced 10/22. Must register by 9/22.

  21. WWW.VIVIT-WORLDWIDE.ORG

More Related