gridwise-webgpu / gridwise-webgpu/gridwise
Potential Issue: Atomic buffers not cleared between trials
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 9
- Avg merge
- 9m
- Merged PRs (30d)
- 6
Description
This line is executed repeatedly when running multiple trials (params.trials > 1), but the underlying atomic buffers are not cleared. As a result, atomics may accumulate values, causing decreasing performance or incorrect results after several runs.
I’ve attached a screenshot showing the atomic values of spineBuffer and scanBump over multiple trials for reference.
Possible solution: Clear atomic buffers after each trial
After clearing it :
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.
Research direction
Start at examples/scan_sort_perf.mjs around line 289 and trace the repeated trial path when params.trials is greater than 1. Verify how spineBuffer and scanBump are used between trials, then confirm that repeated runs no longer accumulate atomic values and still produce correct results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100