arrayfire / arrayfire/arrayfire-benchmark

support int32 and int64 operations in all benchmarks

Abierto
#21 1 comentario 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

Modern GPUs are doing excellent jobs for int32/fp32 but at least with NVidia and possibly AMD are underperforming on int64 which has significant impact on some applications, whether they be fixed point, time keeping, or workhorse types for algorithms such the numeric types reproblas is built on. I can understand in some cases why fp64 is doing bad but int64 has no excuse when int32 performs so many times faster.

Of course maybe these guesses are incorrect, I've only heard of them as heresay.

This issue calls for each benchmark to be extended to support int32/int64 which may help people understand which GPUs will work for what applications better.

Maybe add an option for dividing up which classes you care about, if you want to preserve the existing subset of functionality (like if you didn't want to run 2x as many tests...)

Guía de contribución

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

Línea de trabajo

No files or benchmark entry points are named. Start by inventorying the repository's benchmarks and running the existing suite to understand how types are selected. Done means every benchmark supports int32 and int64, with an optional way to preserve the existing subset if needed.

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

Evaluación

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

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.