arrayfire / arrayfire/arrayfire-benchmark

support an option to run at the default max problemSpace

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

描述

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.

貢獻指南

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

研究方向

檢查 PR #18,以及現有對 problem-space 引數和每個測試預設值的處理。確定新選項應如何選取現有預設 problem space 中最大的一個,然後驗證較小的測試大小會被排除,且只會產生預期的 plots。

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

評估

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

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

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