Update python benchmarks to use direct bindings.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- performance
Research direction
Start with benchmarks/python/core.py and the Python benchmark test files, then review the FusionDefinition API differences described in the issue. Run !test --pybench, including the benchmarks/python/host cases if retained. Done means the Python benchmarks use direct bindings and the benchmark CI command passes.
Written by the indexing model from the issue text.
Description
We need to update the python benchmarks to use the direct bindings. I'd recommend updating the test files that only need updates to their FusionDefinition before updating core.py.
- CI command:
!test --pybench
General
- Replace
import nvfuserwithimport nvfuser_direct as nvfuser
Update core.py in benchmarks/python
- Direct bindings does not use
FusionCache. Remove frombenchmarks/python/core.pyand update benchmarks appropriately. - Direct bindings does not support
profileargument infd.execute.profilingwas disabled for CUDA 13. Either add profiling to direct bindings or remove option from benchmarks. benchmarks/python/hosttests theFusionCache, so you can make a copy ofcore.pyjust for these tests OR remove the completely.
Update FusionDefinition for benchmarks.
There are some API Differences between direct and legacy bindings. Update FusionDefinition so they run correctly.
- Replace
fd.define_vectorwith regular python list.
V6 = fd.define_vector([T0.size(0), 1], dtype=DataType.Int) # Not Implemented in direct bindings
V6 = [T0.size(0), 1] # Replace with regular python list
- Replace
fd.add_output(output, stride_order)with
output = fd.stride_order(a, stride_order)
fd.add_output(output)
- Dominant language
- C++
- Stars
- 404
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 NVIDIA/Fuser
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Multi-GPU
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Multi-GPU
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Multi-GPU
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·