Skip to content

Solver KPIs #316

Description

@hardyjosh

There has been much back and forth, and a couple of false starts regarding KPIs (see #82, #213)

We now have a pretty clear idea of what the absolute MVP looks like for measuring our solver.

The following KPIs are intended to be simple to measure and capture performance via the lens of what actually matters for users.

KPIs

These should be measured by a separate process to the solver itself. It doesn't even need to be realtime, being able to run these on CLI for a historical period would be preferable to start with.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions