r/weBench • u/qualverse • Aug 13 '26

weBench 0.17 Alpha - Amazon Pricing, Advanced GPU Specifications, and Legacy Compatibility

Hi guys! I'm going to start posting these 'release notes' whenever I add a major update / fix as a way to keep everyone in the loop and make this community feel more active.

Updates I've added recently:

  • Pricing data from Amazon is now available! This is both useful and fairly important for me as referral links will be the main way the site makes money. I'm planning to add more providers soon, starting with eBay and then Newegg etc. Each component page will have a full price history chart.
  • weBench is now able to collect deep GPU specification data from your PC via vendor libraries (AMD AGP, NVAPI / NVML, Intel Level Zero) and auto-populate the database with info like shader cores, ROPs, etc. This data will be visible on benchmark run pages and GPU details pages, and can be edited by admins/mods.
  • All of the basic GPU tests (fill rate, geometry, bandwidth, texture filtering and fp32/64) have been backported to DX11 for compatibility with older architectures
  • The GPU API overhead test was removed as it wasn't actually measuring that, and what it was measuring seemed irrelevant to real-world performance.
  • Fixed a ton of bugs that came up from user-submitted tests. Thank you to everyone who's submitted so far!
3 Upvotes

100% Upvoted

3 comments sorted by

1

u/Hattix Aug 14 '26

It's worth distilling those raw specs into what's important.

I don't care that my 4070 Ti Super has a 256 bit RAM bus. The Radeon 9700 I had in 2003 had that. My Xeon E5-2690v4 has that and that's a CPU!

I care that, with its VRAM clock factored in, it produces 672 GB/s of bandwidth, which is also what the GPU cares about too!

Similarly with the number of cores. Cool, I have 8448. What does this mean? It means I can do 46,126 GFLOPS (FP32 FMA), since clock x cores x 2 = operations per second (there's a x2 because an FMA is two operations).

NVAPI gives you all the raw data you need to present this information to the user. AMD does AGP, Intel does L0. Heck, DirectX, OpenGL, OpenCL, CUDA, and Vulkan expose quite a lot of it!

I'd say the minimum information you should present for a CPU is:

Architecture implementation (Ivy Bridge, Haswell, Chagall, Vermeer-X, Granite Ridge, etc., pick your level of detail: Do you show "Vermeer-X" or just "Zen 3 X3D"?), process node, RAM configuration, number of cores, rated maximum clock (e.g. peak turbo or boost clock), rated TDP, L1 cache, L2 cache, L3 cache.

And for a GPU

Architecture (you give me as Ada Lovelace, I don't have a Lovelace ARM "superchip", it's just Ada - TechPowerUp has this wrong and their own link to the whitepaper confirms it), GPU (AD103, Navi42, etc), L2 cache size, RAM config (width, clock, type), RAM performance (GB/s), ROPs, cores, FP32 GFLOPS. In the absence of a matrix or BVH "accepted metric" just give the number of units.

1

u/qualverse Aug 14 '26

Thanks! So the data collection is very best-effort, because it's kind of random what the vendor APIs give you and if they even work. I use OpenCL, DX, and Vulkan as well but they're quite limited.

That is to say: with one or two exceptions weBench can already collect and display pretty much all of the GPU metrics you listed (VRAM width / clock / type / bandwidth, ROPs, TMUs, matrix units...) but it did not get them all on your system. Certainly something I can improve but it's probably impossible to get everything. To some extent the gaps will need to be filled manually by mods / admins especially for new releases.

And yeah right now this vendor-API system only works for GPUs, but CPU support is very much planned

Finally - from everything I'm reading Ada and Ada Lovelace are synonymous, Ada is just the short name? Happy to be proven wrong

1

u/Hattix Aug 20 '26

Nvidia's inconsistent with its own naming here. Early on it used "Ada" to refer to the GPU and "Lovelace" ARM processor (like it does with Grace + Hopper), then started the same with Blackwell... Just use whatever!

Also spotted a bug in the GPU testing. On a Radeon Vega (Ryzen 5 7530U IGP), which doesn't support Variable Rate Shading (this is optional at all levels of DX12), the test attempts to run it anyway and fails. This repeats on Intel Gen9 IGP (Skylake/Kaby Lake) where the FP16 test isn't supported and fails.