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!) I just wanted to have an idea of the general expectation for DHAT overhead. > 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? Red Hat Enterprise Linux Workstation release 6.5 (Santiago) gcc (GCC) 5.3.0 for the test executable. gcc version 9.2.0 (GCC) for building Valgrind, built from git HEAD. The server has 48Gbytes of RAM and only about 6Gbytes is being used. The executable is quite big text data bss dec hex filename 57369168 417156 20903108 78689432 4b0b498 [snip] The run under DHAT is using about 2Gbytes virtual and 1.5Gbytes resident according to htop. Running standalone those are about 750M and 350M respectively. I'll have to find a much smaller test before I consider doing any profiling of DHAT. I'll also try nullgrind to see if it really is the DHAT instrumentation overhead that is slowing things down. A+ Paul _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
