Skip to content

Commit

Permalink
Merge pull request #550 from ShriyaPalsamudram/shriya/benchmark_lifec…
Browse files Browse the repository at this point in the history
…ycle

Formalize rule regarding benchmark lifecycle
  • Loading branch information
hiwotadese authored Nov 21, 2024
2 parents d38fe44 + 285f4e1 commit af986e2
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions training_rules.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,14 @@ The benchmark suite consists of the benchmarks shown in the following table.

|===

### Benchmark Lifecycle

Developing high-quality benchmarks requires significant effort, computational resources, and commitment. Therefore, each benchmark is expected to remain part of the benchmark suite for a minimum of two years or four submission rounds, whichever comes first.

A benchmark may be considered for early retirement due to reasons such as, but not limited to, low industry adoption. Early retirement requests will be reviewed by the Training working group, followed by a formal vote to determine the benchmark's status.

### Benchmark reference implementation

MLCommons provides a reference implementation of each benchmark, which includes the following elements:

Code that implements the model in a framework.
Expand Down

0 comments on commit af986e2

Please sign in to comment.