NVIDIA/Fuser

Pointwise heuristics incorrect memory access estimation

Open

#4,773 opened on Jul 11, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (80 forks)github user discovery
good first issue

Repository metrics

Stars
 (392 stars)
PR merge metrics
 (PR metrics pending)

Description

Hmm... I don't think the original code of this part makes sense. The unit of cur_transfer_size and right_transfer_size were in the unit of byte ^ N, where N is the number of dimensions on the left/right of the break point. My PR will change it to bit ^ N, so in this sense, my PR is NOT a no-op. But I believe we should not block my PR because of this. Instead, we should fix it in a later PR.

Originally posted by @zasdfgbnm in https://github.com/NVIDIA/Fuser/pull/4748#discussion_r2199798284

Contributor guide

Research direction
Examine the pointwise heuristics in the Fuser codebase, focusing on the memory access estimation logic for cur transfer size and right transfer size. Identify where the unit conversion from byte^N to bit^N is incorrectly implemented and propose a fix.
Tech stack
ccpp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++CUDA
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70