← Latest papers
🔢 mathematics

Benchmarking Optimization Algorithms with Quality Profiles and Test Set Profiles

This paper introduces novel benchmarking tools called quality profiles and test set profiles to evaluate optimization algorithms based on solution accuracy rather than computational cost, while also assessing the appropriateness of test sets, with validation provided through extensive numerical experiments and accompanying MATLAB code.

Original authors: G. Fasano, C. Piermarini, M. Roma

Published 2026-07-21✓ Author reviewed
📖 4 min read🧠 Deep dive

Original authors: G. Fasano, C. Piermarini, M. Roma

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a coach trying to figure out which of your athletes is the best runner. You don't just care about who finishes the race first; you also care about how they finished. Did they sprint across the finish line with perfect form, or did they stumble and cross it barely standing up? In the world of computer science, specifically a field called optimization, algorithms are the athletes. Their job is to find the "best" answer to a complex math problem, like finding the lowest point in a mountainous landscape. Traditionally, coaches (researchers) have mostly timed the runners to see who is fastest (efficiency) or counted how many times they successfully finished the race (reliability). But what if two runners finish at different spots on the mountain? One might be at the very bottom (the perfect answer), while the other is just a little way up the slope. If you only look at the time, you might miss the fact that one runner actually found a much better spot. This is the puzzle this paper tackles: how do we fairly compare runners who end up in different places, and how do we know if our race track (the set of problems we give them) is actually a good test?

The authors, Giovanni Fasano, Christian Piermarini, and Massimo Roma, introduce two new tools to solve this: Quality Profiles and Test Set Profiles. Think of Quality Profiles as a special scoreboard that doesn't just measure speed, but measures "how close to the perfect answer" each algorithm got. Instead of asking, "How long did it take?", it asks, "How much better is this solution than the starting point?" It allows researchers to zoom in on the details, seeing which algorithm consistently finds the deepest valleys in the mathematical landscape, even if they take different paths to get there. This is crucial because sometimes, the fastest algorithm isn't the one that finds the best answer.

The second tool, Test Set Profiles, is like a quality check for the race track itself. Imagine you are testing runners, but you only give them a race on a flat, boring track. You might think your runners are amazing, but they've never faced a real challenge. The authors realized that sometimes the list of problems we use to test algorithms (the "test set") might be too easy, too hard, or just not representative enough. Their new tool uses a statistical trick called "bootstrapping" (which is like running the same race over and over again with slightly different groups of runners to see if the results hold up) to measure how reliable the test track is. If the results change wildly when you swap out a few problems, the test set isn't very reliable.

In their experiments, the authors tested these tools on two types of challenges: smooth, predictable problems (like rolling a ball down a gentle hill) and rough, jagged problems (like navigating a rocky cliff without a map). They found that the new Quality Profiles were excellent at showing which algorithms truly found the best solutions, even when the algorithms were very different from each other. For instance, they showed that some algorithms were great at finding the bottom of the hill quickly, while others were better at finding the absolute deepest spot, even if it took a bit more effort. They also discovered that the size of the test set matters: if you only test on a few problems, your conclusions about which algorithm is "best" might be shaky. But with a larger, well-chosen set of problems, the results become much more stable and trustworthy.

Ultimately, this paper doesn't claim to have found the single "best" algorithm for every problem. Instead, it offers a better way to look at the race. It suggests that we shouldn't just look at the stopwatch; we need to look at the finish line location and make sure the track we're running on is fair and challenging enough. By using these new profiles, researchers can get a clearer, more honest picture of how their algorithms really perform, ensuring that the "winners" are actually the ones who found the best solutions, not just the ones who ran the fastest on a lucky day.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →