1650153 - Expose performance properties for simple (or complex!) filtering

Status: NEW

(Tree Management :: Perfherder, enhancement, P3)

Description

[Kyle Lahnakoski [:ekyle]]

Currently we can only pull performance dataum by signature. We would like to pull performance datum by their properties; pull multiple signatures with a single query without knowing the actual signature. Removing the need for a signature is good because dashboards can specify what is wanted directly. For example, pull performance suite by name without concern for the framework it belongs.

We would like to include all properties found in the perf_datum table and perf_signature` table, but we can start with a minimum list:

        'repository',
        'suite',
        'test',
        'framework',
        'platform',
        'option_collection',
        'extra_options',
        'application',

This can be implemented as a traditional REST parameters, but we should have a plan of supporting Boolean combinations of filters; which my experience has told me will be demand shortly after this feature is available.

Comment 1

[Kyle Lahnakoski [:ekyle]]

https://bugzilla.mozilla.org/show_bug.cgi?id=1642362 is a general problem with test renamaing. A specific solution is to add a url parameter to tests and allow searching on that parameter.

Comment 2

[Kyle Lahnakoski [:ekyle]]

https://bugzilla.mozilla.org/show_bug.cgi?id=1649551 would like to add job_type to the signature. The solution is to add job_type to the perf_dataum table. It can also be exposed as a searchable property.

Comment 3

[Kyle Lahnakoski [:ekyle]]

The health graphics dashboard downloads all the signatures, runs a property filter to find the signatures, and then requests the signatures. The filter takes a long time on the Javascript side (as it loops through 100K signatures running multiple expressions). This would be more efficient if the filter was sent to the database and the datums returned directly.