Performance Co-Pilot (PCP) is an open-source distributed system performance analysis toolkit. It efficiently collects metrics from multiple systems and provides a variety of web, graphical and console tools for analysis of live and historical data.
The suite begun production use over 20 years ago primarily in the High Performance Computing arena, however its customizable and lightweight design has proven popular on everything from tiny system-on-a-chip machines through to vast databases and number-crunching super computers. It is included in all Linux distributions and has an active base of users and developers.
Writers interested in contributing to the project described here are encouraged to contact the volunteers listed below, and join the PCP community for further discussion.
Three volunteers have come forward to assist once again - a PCP maintainer, a developer and a documentation specialist - all of whom volunteered last year as well.
In our previous Google Season of Docs project, we converted two freely-available books (the "Users and Administrators Guide" and the "Programmers Guide") into pcp.readthedocs.io content. We also extended this documentation with a new REST API guide, and made many other improvements.
However, due to the many available tools, daemons, integrations and APIs we still find a high barrier to entry for new PCP users.
It is this we plan to tackle next with our writer - curating a new series of focussed, task-oriented "How To" guides that will assist new users in engaging immediately, by clearly showing how to solve specific problem scenarios that users encounter frequently.
The goals of the project are this to assist first-time users to become more productive right away, while also increasing traffic to the more detailed books in the same location (readthedocs.io). We plan to undertake this project over three months.
Pair developers with the writer to produce succinct step-by-step recipes showing how to perform certain tasks with PCP.
Task-based topics include:
How do I ...
Additionally, the writer will:
Work that is out-of-scope for this project:
This project will focus on core PCP functionality, and not on integration with (for example) 3rd party sources of metrics, or sending PCP metrics to other analysis systems.
We anticipate the How To pages will provide a better suited entry point for both new and some existing users. We will measure this by first enabling Google analytics on our readthedocs pages to begin tracking page accesses.
Success will be indicated by: