arrayfire / arrayfire/arrayfire-benchmark

support an option to run at the default max problemSpace

Ouverte
#19 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
C++
Étoiles
6
Forks
6
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
cpp
Domaine
cli, performance
Type d'issue
Fonctionnalité
Difficulté
3/5
Temps estimé
1-2 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.