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 摘要。