7950x results: with Intel OCL runtime with dot product ext supp. way slower than without it..
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- performance
Research direction
No files, tests, or entry points are mentioned. Start by reproducing the INT8 benchmark on the Intel OpenCL runtimes 2025.1 and 2024.x using the reported Ryzen 9 7950X setup, then determine whether the regression is in the benchmark or the runtime. Done means documenting the cause and an actionable project change or confirmed external-runtime issue.
Written by the indexing model from the issue text.
Description
Hi,
similar situation to M4.. i.e. CL runtime supporting cl_khr_integer_dot_product produces slower results
new Intel OpenCL runtime for CPU 2025.1 supports cl_khr_integer_dot_product! (https://www.intel.com/content/www/us/en/developer/articles/release-notes/opencl-runtime-release-notes.html)..
results on 7950x on 2025.1:
| INT8 compute 0.079 TIOPs/s (1/64) |
vs using older 2024 runtime not supporting it:
| INT8 compute 0.588 TIOPs/s (1/64) |
full results:
2025.1:
|----------------.------------------------------------------------------------|
| Device ID | 1 |
| Device Name | AMD Ryzen 9 7950X 16-Core Processor |
| Device Vendor | Intel(R) Corporation |
| Device Driver | 2025.19.3.0.17_230222 (Windows) |
| OpenCL Version | OpenCL C 3.0 |
| Compute Units | 32 at 0 MHz (16 cores, 0.000 TFLOPs/s) |
| Memory, Cache | 98026 MB RAM, 1024 KB global / 256 KB local |
| Buffer Limits | 98026 MB global, 128 KB constant |
|----------------'------------------------------------------------------------|
| Info: OpenCL C code successfully compiled. |
| FP64 compute 1.100 TFLOPs/s (1/64) |
| FP32 compute 1.309 TFLOPs/s (1/64) |
| FP16 compute 0.244 TFLOPs/s (1/64) |
| INT64 compute 0.538 TIOPs/s (1/64) |
| INT32 compute 1.270 TIOPs/s (1/64) |
| INT16 compute 2.589 TIOPs/s (1/64) |
| INT8 compute 0.079 TIOPs/s (1/64) |
| Memory Bandwidth ( coalesced read ) 50.96 GB/s |
| Memory Bandwidth ( coalesced write) 27.70 GB/s |
| Memory Bandwidth (misaligned read ) 60.71 GB/s |
| Memory Bandwidth (misaligned write) 30.80 GB/s |
|-----------------------------------------------------------------------------|
2024.x:
|----------------.------------------------------------------------------------|
| Device ID | 1 |
| Device Name | AMD Ryzen 9 7950X 16-Core Processor |
| Device Vendor | Intel(R) Corporation |
| Device Driver | 2024.17.3.0.08_160000 (Windows) |
| OpenCL Version | OpenCL C 3.0 |
| Compute Units | 32 at 0 MHz (16 cores, 0.000 TFLOPs/s) |
| Memory, Cache | 98026 MB RAM, 1024 KB global / 32 KB local |
| Buffer Limits | 98026 MB global, 128 KB constant |
|----------------'------------------------------------------------------------|
| Info: OpenCL C code successfully compiled. |
| FP64 compute 0.979 TFLOPs/s (1/64) |
| FP32 compute 1.175 TFLOPs/s (1/64) |
| FP16 compute not supported |
| INT64 compute 0.303 TIOPs/s (1/64) |
| INT32 compute 1.225 TIOPs/s (1/64) |
| INT16 compute 2.323 TIOPs/s (1/64) |
| INT8 compute 0.588 TIOPs/s (1/64) |
| Memory Bandwidth ( coalesced read ) 49.40 GB/s |
| Memory Bandwidth ( coalesced write) 27.05 GB/s |
| Memory Bandwidth (misaligned read ) 59.32 GB/s |
| Memory Bandwidth (misaligned write) 30.57 GB/s |
|-----------------------------------------------------------------------------|
- Dominant language
- C++
- Stars
- 335
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ProjectPhysX/OpenCL-Benchmark
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ProjectPhysX/OpenCL-Benchmark#38 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ProjectPhysX/OpenCL-Benchmark#35 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ProjectPhysX/OpenCL-Benchmark#32 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
All issues in ProjectPhysX/OpenCL-Benchmark
Similar issues
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ClickHouse/ClickHouse#125522 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-telemetry/opentelemetry-cpp#4697 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
FujiNetWIFI/fujinet-firmware#1921 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
azerothcore/azerothcore-wotlk#28108 ·
Maintainers usually reply within 1 day