Depending on input values, an application can exhibit
different behaviors with respect to resource consumption.
Some of these behaviors involve intensive computations that
are characteristic of performance problems [6]. Naturally,
testers want to summarize the behavior of an AUT concisely
in terms of its inputs, so that they can select input data
that will lead to significantly increased resource consumption
thereby revealing performance problems. Unfortunately,
finding proper rules that collectively describe properties of