Skip to content

Fix/adapter compute label - #5

Merged
dafioram merged 9 commits into
mainfrom
fix/adapter-compute-label
Nov 6, 2026
Merged

dafioram merged 9 commits into
mainfrom
fix/adapter-compute-label

Conversation

@dafioram

@dafioram dafioram commented Nov 6, 2026

Copy link
Copy Markdown
Owner

No description provided.

dafioram and others added 9 commits November 5, 2026 15:02
The panel printed "Compute shaders yes (Sm5)" for DX12 adapters. wgpu reports
a default shader model there rather than the driver's, so the Sm5 looked
measured and was not. The panel now shows only the yes/no answer for compute,
which comes from the real COMPUTE_SHADERS capability.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DS52oJk4dJpQPT7u2QpTr8
Lists the real GPUs the app has been run on, with OS and driver: a GTX 760
(Kepler) on Windows 10, and an RX 6750 XT on Windows 11. Also notes that CI
runs on software devices (Mesa llvmpipe and lavapipe, Microsoft's WARP), which
check code paths but not real-GPU speed.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DS52oJk4dJpQPT7u2QpTr8
The section is for coverage only, so it lists the GPUs and their OS without
driver or test details.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DS52oJk4dJpQPT7u2QpTr8
GTX 760: NVIDIA 475.14, which Windows reports as driver 30.0.14.7514 for DX12.
RX 6750 XT: driver version not yet recorded.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DS52oJk4dJpQPT7u2QpTr8
--list is the quick way to see which adapters a machine has, so it now prints
the driver under each one. Normal test runs print the same output as before.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DS52oJk4dJpQPT7u2QpTr8
The sensor diagnostics printed memory as a raw tuple, for example
"memory: (701284352, 2147483648)". It now reads "memory: 668.7 MiB used /
2.00 GiB", using the same byte formatter as the VRAM readouts. This line is
shown in the GUI log and in the CLI log file.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DS52oJk4dJpQPT7u2QpTr8
GTX 1060 6GB on Windows 10, NVIDIA 560.94 (Windows driver 32.0.15.6094).
RX 6750 XT on Windows 11, AMD 26.7.1 (Windows driver 32.0.21045.1000 for DX12).

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DS52oJk4dJpQPT7u2QpTr8
The VRAM test took its system-memory snapshot before compiling its shaders.
On the GTX 1060 (Vulkan) the system-RAM count then rose by a fixed 64 MiB at
every test size, so every run was flagged as spilled, even at 100 MiB, and
the estimate of what fit in VRAM was wrong.

The snapshot now comes right before the chunks are allocated, so only memory
from the chunks counts toward spill.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DS52oJk4dJpQPT7u2QpTr8
The spill check also counted DXGI's system-RAM growth. That growth includes a
fixed 64 MiB on the GTX 1060 that is not the test's memory, so runs warned even
when every chunk filled at full speed.

- DXGI's counters are now logged for reference only.
- A warning comes only from chunks that fill at under 40% of the fastest
  chunk's speed. The message gives how many chunks slowed and where in the test
  they started, not a "fit" estimate. The start point is not a capacity figure.
- A run that stops early on an allocation error is now WARN, not PASS, since it
  did not test its full target.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DS52oJk4dJpQPT7u2QpTr8
@dafioram
dafioram merged commit 1433013 into main Nov 6, 2026
4 checks passed
@dafioram
dafioram deleted the fix/adapter-compute-label branch November 6, 2026 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant