std::map clear() performance in debugger?

Question

The attached, trivial, test program tests the performance of emptying a simple std::map. Using MSVC 2008 and 2010, the debug build will take <30seconds when executed from a command prompt but almost 3 minutes when executed from within the debugger. The call to clear() is entirely responsible for the difference. If I break into the debugger the callstack will always point to HeapFree.
Question: Why the huge difference? Can I somehow change debug heap settings so it'll be fast when executed in the debugger?

#include <map>

int
main ( int, char )
{
    std::map< time_t, double > test;
    for ( int i = 0; i < 1000000; ++i )
    {
        test[i] = i / 3.14;
    }
    test.clear();
    return 0;
}

score 5 · Accepted Answer · edited Jan 25 '12 at 10:05

5

Trying setting the environment variable _NO_DEBUG_HEAP=1 in the program's initial environment. This disables Windows' internal debug heap, which might make it harder to debug memory corruption problems.

This KB article mentions the flag, and you can infer that the default (low-fragmentation heap) is disabled if the program is run in a debugger without that environment variable. See also this blog post, which discusses how the debug heap can slow down their program by 3-5 times.

edited Jan 25 '12 at 10:05

Suma

33,181
16
123
191

answered Sep 22 '10 at 11:41

Doug

8,780
2
27
37

3

Yes! That's it, thank you. Adding "_NO_DEBUG_HEAP=1" (with leading underscore) to the environment variables fixes the problem. I'll re-enable it periodically for testing, but a factor 100 speed difference for regular debugging is just too much. – BuschnicK Sep 22 '10 at 12:03

wheaties · Answer 2 · 2010-09-22T12:02:09.377

2

The debugger adds a lot of iterator checking for safety. You can disable the iterator checks with the _HAS_ITERATOR_DEBUGGING=0 flag but I don't suggest it. See this blog entry for more information.

edit:

In the response to below, it could if there's debug hooks into the application gathering information to assess the stack or some other process within the debugger monitoring your code. I'm speculating here because I don't know what add-ons you've got installed. However, from the command line you could be using the non-debug executable. I've made that mistake myself and it's easy to do.

edited Sep 22 '10 at 12:02

answered Sep 22 '10 at 11:30

wheaties

35,646
15
94
131

1

Thanks for the answer but the change didn't make a discernable difference. It also wouldn't explain the difference between execution in the debugger vs the command line - or would it? – BuschnicK Sep 22 '10 at 11:54

std::map clear() performance in debugger?

2 Answers2

Linked