[FEA] cluster_cost can accept X norm
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
The cluster_cost could be modified to accept an optional X_norm to avoid recomputing it. That function also synchronize each time it is called, while it would be better to accumulate cluster_cost on device and transfer+sync once at the end.
Contributor guide
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
Locate the cluster_cost entry point and inspect its callers to understand how X_norm and synchronization are currently handled. Check any existing tests covering cluster cost. Done means an optional X_norm can avoid recomputation and repeated calls accumulate on device before a single transfer and synchronization.
Written by the indexing model from the issue text.
Assessment
- Domain
- machine-learning, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100