Ray Reconstruction: slow first start while the kernels compile on a cold driver cache

未關閉
#35 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
cpp

研究方向

Start with Discussion #10, which reports resolve.fixup taking minutes under RADV through Proton, then compare cold-cache kernel startup on Windows and RADV. Identify the slowest kernels and assess whether they can be split or simplified without changing output bits, and whether the launcher or overlay should better indicate preparation. Done means the cold-start delay and candidate improvements or clearer status messaging are documented.

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

描述

area: linux area: ray-reconstruction performance

On the first start, before the driver's shader cache holds Ray Reconstruction's kernels, the frames pass through
undenoised until every kernel of the default frame is ready, which looks like heavy speckle. Discussion #10 reports one
kernel (resolve.fixup) taking minutes through RADV under Proton; later starts are fast. To look at: which kernels take
longest on a cold cache (Windows driver and RADV), whether they can be split or simplified with the same output bits,
and whether the launcher or overlay should say more clearly that Ray Reconstruction is still preparing.

Related: Discussion #10

主要語言
C++
星號
12
分支
2
平均合併
3 小時 10 分鐘
30 天內合併 PR
171

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

phantoslayer21/wronggpu 的其他 Issue

查看 phantoslayer21/wronggpu 的全部 Issue

相似的 Issue

更多 C++ Issue

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

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