On 5/26/20, Paul FLOYD wrote:
I'm running DHAT on what I consider to be a relatively small example.
Standalone the executable runs in a bit under 10 minutes. Based on the CPU time
that we print after every 10% of progress, under DHAT the same executable is
going to take about 422 hours - about two and a half weeks.
Does anyone have any ideas what could be causing it to be so slow?
Please tell us about your environment.
(EVERY query should supply this information!)
Which version of DHAT? Which hardware? Which operating system and version?
Which compiler and version built DHAT? Which compiler(s) built the program
under test?
How big is the program? On a Linux system, run "size ./my_app; ldd ./my_app"
for static size, and "ps alx | grep my_app" for total VIRTual and RESident size.
How much RAM is available for use? How much demand paging is occurring?
There are standard performance tools that apply to EVERY executable program,
not just DHAT. On a Linux system with a DHAT that was built with symbol
information retained ("-g" command-line option to gcc or clang, and
no symbol stripping during static binding by /usr/bin/ld or /usr/bin/strip),
what does 'perf' say?
perf record valgrind --tool=DHAT <<valgrind_args>> ./my_app <<my_app_args>>
perf report > perf_output.txt
A smart user would supply such information in the first post.
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
