arrayfire / arrayfire/arrayfire-benchmark

support an option to run at the default max problemSpace

Offen
#19 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
C++
Sterne
6
Forks
6
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

I plan on implementing this option (tonight) - it'd be great if you could provide quick feedback.

Given that each test has a very different meaning to the problem space (1d vs 2d, algorithm class) - it is difficult to scale something like the problem-space argument I provided in PR #18 across all tests.

What would the argument name be? --use-largest-default-problemspace ?

I need a capability such as this to reduce the amount of information coming from the tests to help give insights into each GPU or platforms strengths and weaknesses, that is all the smaller sizes would just lead to too many plots. The curent defaults inside were already well chosen sizes, so I think we should have a way to leverage them.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Review PR #18 and the existing handling of the problem-space argument and per-test defaults. Determine how the new option should select the largest existing default problem space, then verify that smaller test sizes are excluded and only the intended plots are produced.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
cpp
Bereich
cli, performance
Issue-Typ
Feature
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.