arrayfire / arrayfire/arrayfire-benchmark

support an option to run at the default max problemSpace

Abierto
#19 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
C++
Estrellas
6
Forks
6
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
cpp
Área
cli, performance
Tipo de issue
Nueva funcionalidad
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.