Skip to content

Spike on tracking quality metrics for nvbench comparison scripts #415

Description

@gevtushenko

We should investigate how to track quality metrics for perf comparison:

  • number of ambiguous comparison results
  • number of false positives

After making changes to warmup run number, stopping criterion, and comparison scripts, we should be able to evaluate the change by tracking these metrics.

This issue can be close with an outline of how this tracking can be implemented.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Status
Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions