Skip to content

docs(design): benchmarking system#51

Open
michael-johnston wants to merge 13 commits intomainfrom
maj_benchmark_design
Open

docs(design): benchmarking system#51
michael-johnston wants to merge 13 commits intomainfrom
maj_benchmark_design

Conversation

@michael-johnston
Copy link
Copy Markdown
Member

No description provided.

Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Co-authored-by: Alessandro Pomponio <10339005+AlessandroPomponio@users.noreply.github.com>
Co-authored-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Co-authored-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
@michael-johnston
Copy link
Copy Markdown
Member Author

@christian-pinto any comments?

Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
@michael-johnston
Copy link
Copy Markdown
Member Author

michael-johnston commented Apr 29, 2026

I may modify 2.1 solution as maybe we shouldn’t require resolving all the benchmark packages together as the only reason to do so seems to be for the proposed 2.1 solution and nothing else.

edit: 3.3 solution also relies on this global resolution

Co-authored-by: Christian Pinto <55737893+christian-pinto@users.noreply.github.com>
Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
@DRL-NextGen
Copy link
Copy Markdown
Member

DRL-NextGen commented Apr 29, 2026

No vulnerabilities found.

Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Co-authored-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
@michael-johnston
Copy link
Copy Markdown
Member Author

@christian-pinto @AlessandroPomponio What about this? The aim is to not require resolving all benchmark packages against each other.

  • for REQ 2.1 - in the model.yaml users specify the path to the benchmark packages the model needs to execute the experiments given in the yaml. We can have just package or package+experiments used.
    • Change: No addition of benchmark package via uv, no deps req, no install.
  • for REQ 2.2. - We have two levels. The nexus cliI can list all experiments registered and all the packages. It can't list experiments not used or the details of the experiments as this requires ado+ installing the package. However at any time user can install a package and get more details
    • Change: We use nexus cli not ado for listing - we can't get same detail and validation, this is the price.
  • for REQ 3.3 - same approach as REQ2.1 works as user just gives a path to a benchmark package in a different nexus package

Choice is then between

  1. Users add benchmark package to uv group.
    • Pro: ado takes care of everything. No additional files need to be edited or code written.
    • Con: All benchmark packages have to resolve together
  2. Users add benchmark package info to nexus package metadata.
    • Pro: No (or much less) dependency issues as for benchmarking only the packages for a single model/algo need to be installed
    • Con: Users need to add metadata to a file. Nexus CLI requires additional code. You can't get same detail as with ado CLI.

Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
michael-johnston and others added 2 commits April 30, 2026 15:40
Co-authored-by: Christian Pinto <55737893+christian-pinto@users.noreply.github.com>
Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
@michael-johnston michael-johnston enabled auto-merge (squash) May 2, 2026 13:57
Comment thread docs/design/benchmark_system.md
Comment thread docs/design/benchmark_system.md Outdated
Comment thread docs/design/benchmark_system.md Outdated
Co-authored-by: Alessandro Pomponio <10339005+AlessandroPomponio@users.noreply.github.com>
Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
Comment thread docs/design/benchmark_system.md Outdated
this to the model directory of the relevant nexus package (REQ 2.3). The
benchmark configuration can reference any benchmark experiment registered by the
Nexus package. If the benchmark experiment they need is not registered by the
nexus package [they can add it.](#defining-a-benchmark-to-use-for-a-model). The
Copy link
Copy Markdown
Member

@christian-pinto christian-pinto May 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is referencing the paragraph it belongs to. I assume it is like the below?

Suggested change
nexus package [they can add it.](#defining-a-benchmark-to-use-for-a-model). The
nexus package [they can add it.](#defining-the-benchmark-experiment-packages-used-by-a-nexus-package). The

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@michael-johnston this one is still unresolved.

Co-authored-by: Christian Pinto <55737893+christian-pinto@users.noreply.github.com>
Signed-off-by: Michael Johnston <66301584+michael-johnston@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs (benchmarks): benchmark system design

4 participants