arrayfire / arrayfire/arrayfire-benchmark

support an option to run at the default max problemSpace

Aperta
#19 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
C++
Stelle
6
Fork
6
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
cpp
Ambito
cli, performance
Tipo di issue
Funzionalità
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
35/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.