When creating a piece of software, the measurement of a set of information of interest regarding performance — for instance: CPU time, number of functions evaluated, number of iterations, memory usage, accuracy, or others — is common. Benchmarking is the process of measuring the performance information of one piece of software relative to similar software.
Furthermore, given a set of software that solve the same problem, one could compare them in order to choose the best one, or verify how their own software can be improved. To address this, Dolan and Moré  developed a tool to visualize optimization solvers benchmarks: the performance profile.
Formally, a performance profile allows one to evaluate and compare the performance of a set S of solvers on a given test set P, with respect to a chosen evaluation parameter, which will be referenced as cost. It is presented as a graphic that shows the cumulative distribution function of different solvers performances, according to the chosen cost metric. Note that the cost metric must be positive.
This method is mostly used for nonlinear optimization solvers, however, it is possible to extend it to other software comparison. For instance, some authors have used it in the context of algorithms for matrix functions [5, 6, 7, 8, 12, 13, 14]. Notice that, in some cases, a specialized test can be more significant than the performance profile with a specific cost. For derivative-free optimization, for instance, Moré and Wild  define a data profile, using the number of function evaluations as the metric cost, nevertheless in a different way of performance profile definition.
For each problem p ∈ P and solver s ∈ S, let tp,s be the cost required to solve problem p by solver s and
be the performance ratio of solver s for the problem p when compared with the best performance by any solver on this problem. As a convention, we set rp,s to a large value, say rmax, if the solver s does not solve the problem p.
The probability of a solver s ∈ S to solve one problem within a factor τ ∈ ℝ of the best performance ratio is the function
For a given τ, the best solver is the one with the highest value for ρs(τ), that is, the one with the highest probability to solve the problem. The value ρs(τ) represents the percentage of problems solved by algorithm s with a cost at most τ times worse than the best algorithm. ρs (1) is the percentage of problems solved as fast as the fastest algorithm, which gives the efficiency of solver s. On the other hand
is the total percentage of problems solved by solver s, or in other words, the robustness of solver s.
To facilitate the reproduction of data set analysis, such as benchmarking of solvers analysis provided by Dolan and Moré ’s performance profile, an open source tool that handles the production of performance profile plots should be available.
Performance profile has been, over the years, the most used benchmark comparison tool used in optimization. Nevertheless, the production of such analysis is sometimes a dull task, that can lead a researcher to waste a lot of time and effort that should have been spent in developing the solver itself.
There are other implementations to generate performance profiles, some of them being reasonable well-known, such as a MatLab script from the same group that created performance profile , and a module written by Michael Friedlander inside NLPy .
Some, perhaps unaware of these implementations or trying to avoid proprietary solutions, implemented their own solutions and then made them available. Solutions such as a Python function perfprof from Relton  and a Julia module perfprof.jl from Zhang , both language dependent. A thorough search would possibly reveal many others. However, there are features that some users need that these software have not implemented.
This paper describes a straightforward open source tool that allows one to create performance profile pictures in a fast and easy manner called perprof-py. In addition, this tool allows LaTeX users, a group which includes almost all of the optimization community, to generate performance profile plots as LaTeX code that will be processed later with the rest of their document or standalone PDF when needed.
With these two main goals in mind, perprof-py was developed and implemented in Python 3 with internationalization features and direct LaTeX integration.
Implementation and architecture
Perprof-py was implemented as a Python 3 package and organized to allow addition of new backends. Core files are
- perprof/prof.py that defines a class Pdata that need to be extend for every backend;
- perprof/parse.py that has the parser for the input files; and
- perprof/main.py that has the command line interface.
The incompatibility of perprof-py with Python 2 was due (i) to the fact that unicode processing with Python 2 can be a nightmare, and (ii) to the authors’ desire to push Python 3 forward.
Users have a command line interface to use out of the box, however one can also use the package in their own software.
Implementation is very straightforward. In fact, the algorithm:
- parses the options passed as arguments, creating a structure with all information;
- parses and process input files, using the performance function definition to create data to be plotted;
- uses the chosen backend to plot data.
For each solver to be compared in benchmarking, one must write a file in the following manner:
--- YAML information --- Problem01 exit01 time01 Problem02 exit02 time02
YAML[19, 24] information is a list of keywords and values used to set the name of the solver and some flags for perprof-py. A legacy option remains, in which the user can instead put only the solver name using
#Name SOLVERNAME Problem01 exit01 time01 Problem02 exit02 time02
nevertheless some users may like to add more options.
Each line of data has at least 3 columns. Columns’ meanings, in the default order, are:
- Problem’s name;
- Exit flag;
- Cost measure – for instance, elapsed time.
Default exit flag is c or d on the exit flag column, meaning convergence or divergence, respectively.
One of the perprof-py solver examples uses the following YAML information
algname: Alpha success: converged free_format: True
which means that the name appearing on the profile will be Alpha; that converged is the word that means convergence, and that every other exit flag word means divergence. These options were set from algname, success and free_format options, respectively.
A user can, optionally, add more columns to add information. They can verify, for instance, that the optimality conditions are satisfied for each problem. Also, using either YAML or command line options, a user can change each columns’ meaning. Note that these options are not enabled by default. The user should consult the help and documentation files to see how to enable them.
Parsing process and output
To use perprof-py, one needs to issue a command of the type
$ perprof OPTIONS BACKEND FILES
- FILES are the input files described in the previous section. At least two files input are required;
- BACKEND is one of the options --tikz, --mp, --bokeh or --raw, which represents whether the user wants to use TikZ/PGFPLOTS, matplotlib, Bokeh, or simply printing the performance ratios, respectively;
- OPTIONS are varied arguments that can be passed to perprof-py to customize the graphics or modify the performance functions. Some noteworthy options are
- – --semilog: the natural logarithmic scale is used on the abscissa axis;
- – --success STR: STR is a comma separated string of keys that was considered success by the solver;
- – --black-and-white: perprof-py creates the plots using only line styles and it colors them in black;
- – --subset FILE: perprof-py considers only the subset problems listed in FILE, while creating the performance functions.
In order to demonstrate such OPTIONS, Figures 1, 2, 3, 4 show some examples of performance profile graphics. Figure 1 shows the performance profile graphic with default options. Note that the lines are clumped due to the maximum time allowed in the solver. Figure 2 shows the performance profile using semilog option, which plots the graphic using a log scale on the abscissa. Figure 3 shows the performance profile using also the black and white option, which gives a printer-friendly graphic. Figure 4 shows the performance profile using subset and semilog options. In this case, we selected around 120 problems, put their names in a file, and passed the file with the option. This limits the comparison to only those files.
Perprof-py code is tested using unit tests that verify if incorrect input information is captured. These tests are run automatically on Travis CI , for Python 3.3 and 3.4. In addition, a script is run to generate several performance profile graphics. This script is also run on Travis CI, though the evaluation that perprof-py outputs the desired graphics can only be done locally.
This script uses artificial solver information accessible using --demo as argument in the perprof-py call. For instance, to test that the TikZ installation is successful, one can run
perprof-py --demo -o tmp --tikz
If everything is correct, this will generate a file tmp.pdf with an example performance profile made using LaTeX and compiled to a standalone PDF.
One can run the testing script by entering the folder perprof/examples relative to the package folder, and running
Folder plots will contain the outputs in formats PNG and PDF.
Perprof-py is developed and actively tested on Unix platforms. The authors did not test it on Windows.
The project was built entirely in Python 3.
Additional system requirements
No additional hardware requirements are necessary.
Perprof-py depends on the Python packages matplotlib, pyyaml and bokeh. In addition, if a user wants the PDF image from the LaTeX version, it also requires pdflatex.
GPL (General Public License) Version 3
Abel Soares Siqueira
GPL (General Public License) Version 3
Perprof-py was entirely developed in English, however there is support for other languages in the code. Currently, in addition to English, Brazilian Portuguese is the only other language implemented.
(3) Reuse potential
The implementation of perfprof-py is separated in a way that facilitates the creation of a new backend. The class Pdata is defined to store the parsed data (P, S, ts,p, etc.) and methods are defined to create the profile data rp,s. Backends are classes that extend Pdata defining a method plot which creates the expected figure. One should have little difficulty creating their own backend, specially if one uses a perprof-py backend as a starting point. However, if one wants to change the profile data definition — in order to implement a data profile (see ) —, one would have to modify one or more methods in Pdata directly or re-implement the backends.
The parser opens the input files and creates the information for Pdata. Replacing this parser — to use with perprof-py backends — would not be an easy task since the correct output format should be created. Nevertheless, extending it with additional options would be simple enough.
The entry point perprof-py essentially collects the options from the command line and calls the specific backend profiler. This can be completely bypassed by calling the backend directly. This allows one to create a performance profile from another python application. In particular, a possibility is the creation of a graphical user interface (GUI) or a web server application. Perprof-py modularity allows whoever desires to construct this interface to focus entirely on obtaining the options from the user and passing it to the backend.
Whether one is planning on expanding some of perprof-py functionalities or creating any new backend or interface, one can contact the authors using the project page on GitHub .
The authors declare that they have no competing interests.