I often use a variation of this line of thinking for determining if something is worth optimizing. Sometimes it can be hard to tell from profiling output or fl

I often use a variation of this line of thinking for determining if something is worth optimizing. Sometimes it can be hard to tell from profiling output or flame graphs just how much time is spent somewhere. Before trying to make something faster the first thing I do is turn it into a no-op. If avoiding doing something entirely makes the program run 2% faster, then making that run in half the time is only going to give an overall 1% improvement. I don't know if there's a name for this variation. It's just the same thing applied to different components and not specifically related to parallelism.