I'm trying to track down a problem in a big C project where we sometimes run out of heap space during the build. vcperf is nice but it focuses solely on CPU usage and how long files/functions take to build.
I want to look at memory usage over time and see what step in the build is involved when it gets too high.
The best I can do now is separately record memory usage and merge the ETL's, but I haven't found a way to do it reliably and it's much more cumbersome. For example, just running wpr with "GeneralProfile" records too much over a 15 minute build and we lose interesting data.
I'm trying to track down a problem in a big C project where we sometimes run out of heap space during the build. vcperf is nice but it focuses solely on CPU usage and how long files/functions take to build.
I want to look at memory usage over time and see what step in the build is involved when it gets too high.
The best I can do now is separately record memory usage and merge the ETL's, but I haven't found a way to do it reliably and it's much more cumbersome. For example, just running wpr with "GeneralProfile" records too much over a 15 minute build and we lose interesting data.