The topics covered in this HowTo are:

  1. Introduction
  2. What are HowTo’s
  3. Why HowTo’s @ PPA
  4. Why did we write this HowTo
  5. What can you expect to learn from this HowTo
  6. Agile Testing Quadrants and Performance testing
  7. Why use a tool for Performance testing?
  8. What are the different types of Performance Tests one could perform with a Performance Testing tool?
  9. Does my choice of Performance Tests impact my choice of tools?
  10. Dimensions to consider when selecting A Performance Testing Tool
  11. What Are My Options: Open Source & Commercial?
  12. Protocol Support: What Protocol I Am Going to Need to Record My Scripts In?
  13. What Are the Factors That Affect Tool Licensing Models?
  14. What Fancy Workload Models Will I Need To Design?
  15. What Concurrency Should the Tool Support?
  16. What Scalability Considerations Should I Have In Mind?
  17. Does My Enterprise Need Customer Support
  18. How Much Is My Enterprise Willing To Spend i.e. Commercial v/s Open Source tools?
  19. How Much of Development Effort Are You Willing To Spend on Your Scripts (i.e. Commercial v/s Open Source tools)?
  20. Am I Expecting to have Automated Correlation, Parameterization & Analysis Capabilities Built into the Tool?
  21. Is this a Silo i.e. Project specific or an Enterprise Investment?
  22. What Deployment Architectures are supported?
  23. Does The Tool Need to Integrate with Monitoring & Diagnostics solutions?
  24. What Are the Training Options Available For the Tool You Are Considering?
  25. What Are the License Costs?
  26. How Strong Is the Vendor/Community Ecosystem & Vendor Support?
  27. Is The Tool Devops friendly and Does It Integrate with CI/CD PIPELINE?
  28. Conclusion

What Are HowTo’s

A HowTo is a document that does precisely what the name suggests i.e. It’s describes “HowTo” achieve a set of outcomes through illustration of all the steps involved. HowTo’s are generally structured and written without too much technical jargon in a straight forward manner without making too many assumptions of the depth of knowledge the reader. HowTo’s are meant to make for easy reading and are logical in the sequence of steps it recommends.

Any background knowledge required to assimilate the information provided in the HowTo is generally highlighted at the start of the HowTo. HowTo’s are generally written for the professional who are clear of what they need to accomplish but have little or no knowledge of how to go about achieving those objectives. HowTo’s are meant to be exhaustive in nature and they are definitely not meant to offer the most efficient way of getting the job done. A HowTo should be seen as a kick starter that helps the user get up and running with a given task without having to master all the required fundamentals.

 Why HowTo’s @ PPA?

HowTo’s have been the mainstay of the Open Source and Free Software movement for decades. One of the reasons why Open Source and Free Software is so widely used today is simply because of the depth of documentation that exists and the maturity of the Open Source ecosystem which has delivered scalable, open and reliable software. HowTo’s like many other building blocks have helped the Open Source and Free Software movement grow immensely while eliminating the need to keep re-inventing the wheel. It’s only natural that we at Practical Performance Analyst adopt the best from the Open Source and Free Software movement. A lot of the work we do at Practical Performance Analyst borrows from the fundamentals of the Open Source movement and HowTo’s are definitely one of them.

As HowTo’s @ PPA grows and matures we will hopefully reduce the reinventing of the wheel which happens so very often at organizations, projects and programs when it comes to the science of building/delivering systems that scale.

Links to Content

 Trevor Warren (Linked In) focuses on building innovative solutions that have the potential to impact people’s lives in a positive manner. Trevor is inquisitive by nature, loves asking questions and sotrevor_warrenmetimes does get into trouble for doing so. He’s passionate about certain things in life and building solutions that have the ability to impact people’s lives in a positive manner is one of them. He believes that he can change the world and is doing the little he can to change it in his own little ways. When not hacking, building new products, writing content for Practical Performance Analyst, dreaming up new concepts or building castles in the air, you can catch-him bird spotting (watching planes fly above his house). You can reach trevor at –  trevor at practical performance analyst dot com. The views expressed on this web site are his own.

Thank You For Visiting & See You Soon

Practical Performance Analyst - NewsLetter

Signup and Stay In Touch

Signup to the Mailing List here at Practical Performance Analyst and Stay In Touch. We promise not to SPAM you.