Skip to content

Reports we should generate for periodic benchmark jobs #5

@jrevels

Description

@jrevels

From discussion here:

Does it make sense to run against previous release as well. I'm thinking else, regressions could be introduced bit by bit were each part is small enough to dissappear in the noise.

After we gather enough nightly data, we'll be able to start looking at trends over longer time intervals, which helps with this. My idea was to have @nanosoldier generate a weekly/monthly report using the existing benchmark data, in addition to the daily reports. Then we'd have daily comparisons, weekly comparisons, and monthly comparisons, as well as the data to do more advanced trend analysis later on.

We can simply run the benchmarks for the current stable release once, and reuse that data when doing comparisons. Then we could just generate report_vs_release.md in addition to our current report.md.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions