c++ - vsinstr.exe instrumented large executable performance -


i use visual studio vsinstr.exe tool instrumenting unmanaged c++ executable (legacy app). large project , way how map our huge test automation content actual code, identify test cases affected when change made code base.

i'm concerned performance of such instrumented executable, because need run whole test automation content coverage data (or update when code changed) , done each night. picture, test automation run takes maybe 10 hours (gui tests, no unit tests because of legacy architecture)

does have real experience regarding performance of instrumented executables?

i realize question getting long in tooth (getting old) answer intended other users stumble across question.

from real world experience, instrumented binaries run slower, orders of magnitude. however, have instrumented managed binaries , op stated unmanaged c++ "your mileage may vary."

my suggestion run subset of tests take between 2-3 minutes. run subset 3 times , average actual run time results. instrument binaries , run same tests 3 times , compute average. fewer tests , data might skewed because of application initialization. more tests , may end waiting hour each instrumented test.


Comments

Popular posts from this blog

html - How to style widget with post count different than without post count -

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

javascript - storing input from prompt in array and displaying the array -