mlpack / mlpack/benchmarks

Include version information in database

Open
#42 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
107
Forks
46
PR merge metrics
No merged PRs in 30d

Description

Ideally a user who is looking at the benchmark results should be able to determine what version of each library was used for benchmarking. This might be as easy as grabbing the version information fromt he configuration, or it might be a little more difficult---for the 'performance over time view', we may want to also update that to get the version at the time of each run and display that.

I'll handle this when I have time (unless someone else gets to it first).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the database schema, benchmark configuration, and performance-over-time view, then determine how versions can be recorded for current and historical runs. Done means benchmark results identify the version of each library used, including versions for past runs where the historical view displays them.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.