arrayfire / arrayfire/arrayfire-benchmark

support int32 and int64 operations in all benchmarks

未關閉
#21 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
C++
星號
6
分支
6
PR 合併指標
30 天內沒有已合併 PR

描述

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...)

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

沒有指定檔案或基準測試進入點。首先盤點儲存庫中的基準測試,並執行現有測試套件,以了解型別是如何選取的。完成的標準是每個基準測試都支援 int32 和 int64,並且在需要時提供一種可選方式來保留現有子集。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
cpp
領域
performance
Issue 類型
功能
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
30/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。