Before revision:  Though code profiling can determine the location of a performance issue or bottleneck, we posit that the code change required to improve performance may not always be found at the same location. Developers must frequently trace back through a program to understand what code is contributing to a bottleneck. We seek to highlight code which is likely causing or has the most effect on the overall execution cost of a program .
After revision:  Though code profiling can determine the location of a performance issue manifests, we use mutation analysis to show where a performance improvement is likely to exist. We find that mutation analysis can indicate locations within a program which are highly impactful to the overall execution cost of a program .