A Benchmarking and Performance Analysis Framework
The code base includes three sub-systems. The first is the collection agent,
pbench-agent, responsible for providing commands for running benchmarks
across one or more systems, while properly collecting the configuration data
for those systems, and specified telemetry or data from various tools (sar,
vmstat, perf, etc.).
The second sub-system is the pbench-server, which is responsible for
archiving result tar balls, indexing them, and unpacking them for display.
The third sub-system is the web-server JS and CSS files, used to display
various graphs and results, and any other content generated by the
pbench-agent during benchmark and tool post-processing steps.
The pbench Dashboard code lives in its own repository.
Instructions on installing pbench-agent, can be found
in the Pbench agent installation guide.
For Fedora, CentOS, and RHEL users, we have made available COPR
builds for the
pbench-agent, configtools, pbench-server, pbench-web-server
and some benchmark and tool packages.
This assumes that somebody has already installed the server bits. The procedure to do that is described in the Pbench Server Installation guide.
You can install the web-server sub-system on the machine from where you
want to run the pbench-agent. That allows you to view the graphs before
sending the results to the server, or even if there is no server to which to
send the results. See the Pbench web server installation guide.
You might want to browse through the rest of the documentation.
Refer to the Pbench User Guide.
TL;DR? See TL;DR - How to set up pbench and run a benchmark of the Pbench User Guide for a super quick set of introductory steps.
The latest source code is at https://github.com/distributed-system-analysis/pbench.
The pbench dashboard code is at https://github.com/distributed-system-analysis/pbench-dashboard.
Yes, we use Google Groups
Yes, we are using GitHub Projects. Please find projects covering the Agent, Server, and a project that is named the same as the current milestone.