torch.profiler schedule produces overlapping traces and inflated kernel times — how to configure it correctly
I'm using torch.profiler with the Kineto backend (PyTorch 2.x) to find GPU bottlenecks in a training loop before attempting any optimization. The goal is a clean, steady-state trace of a few representative iterations that I can inspect in TensorBoard, without the profiler itself distorting the numbers I'm trying to measure. Two things are unclear. First, the
pytorch