Launching HowTo’s – We have just launched a new section here at Practical Performance Analyst called HowTo’s. Howto’s much like their counterparts (in the Open Source movement) will focus on the specifics around different SPE (Systems Performance Engineering) related tasks. There is a lot of work to be done and we’ve just got started. This section like most others at Practical Performance Analyst has come together because of the efforts of many volunteers and authors who help us put together and manage the Open BoK (Body Of Knowledge) here at Practical Performance Analyst. To know more about what HowTo’s are and how you could benefit form them please continue reading.
What are HowTo’s – Wikipedia defines How-To’s as follows, “A HowTo is an informal, often short, description of how to accomplish a specific task. A how-to is usually meant to help non-experts, may leave out details that are only important to experts, and may also be greatly simplified from an overall discussion of the topic. How-tos have a long history as a way of sharing knowledge on the Internet, but are less successful than FAQs, manuals, recipes and guides.
In the beginning, most howto’s on the Internet were the result of a complex process in which an author wrote a how-to for potential readers. After 2001, user added content played a more and more important role on the internet in a trend that is widely referred to as Web 2.0. This had a profound impact on the way in which howto’s are generated on the internet, as the readers and users were able to add to and improve the on-line content.”
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 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.
How To Library: Putting together all the documentation at Practical Performance Analyst has been a fun filled and tremendously fulfilling endeavor. However this involves a lot of effort all thanks to our volunteers here at Practical Performance Analyst. This section provides a listing of all the HowTo’s we intend to put together over the coming year. Feel free to drop us a note at howtos at practical performance analyst dot com and let us know if there’s anything else you would like to see included in the HowTo section here at Practical Performance Analyst.
We hope you find the content useful here at HowTo’s @ PPA. If you have the inclination to support development of the community here at Practical Performance Analyst and contribute to building of the Open BoK (Body Of Knowledge) on SPE (Systems Performance Engineering) please drop us a note at volunteering at practical performance analyst dot com.
What Is HowTo Define Performance Budgets all about – This HowTo deals with the specifics around defining your own Performance Budget. Performance Budgets loosely defined are targets you set for each of your tiers as part of the Non Functional Requirements modelling process. Performance Budgets focus on identifying tier specific targets which developers or systems administrators would take ownership of and deliver against. Performance Budgets would generally apply to each of the following solution components i.e. application components, network components and infrastructure components.
The topics covered in this HowTo include:
- What are HowTo’s
- Why HowTo’s @ PPA
- Why We Wrote HowTo Create A Performance Budget
- What Are Non Functional Requirements
- So What Are Performance Budgets
- What Tiers Should Be Considered In Scope When Defining Performance Budgets
- How Does Performance Budgets Align With Non Functional Requirements
- How Important Are Performance Budgets
- Who Should Own, Design and Maintain Performance Budgets
- At What Point In The Development Life Cycle Should Performance Budgets Be Created
- Let’s Create A Performance Budget
- What Outcomes Should You Expect To Achieve With Performance Budgets
- Measuring and Tracking How Teams Are Tracking With Their Performance Budgets
- Caveats And What To Be Careful Of When Designing Performance Budgets
You can read the entire “HowTo Create Performance Budgets” article at Link.
You can see the entire “HowTo’s” section through this Link.
At Practical Performance Analyst we always have welcomed and respected your input, feedback and comments. In fact, we are keen to work with experienced Performance Architects, Performance Engineers, Performance Testers, Capacity Planners who might want to write their own HOWTO’s or partner on writing a HOWTO. Also, if you have ideas that you think should be on this list please send us an email with details of the topic and why it should be included in this list.