3 ms·
I never did figure why the author insisted on reporting the runtime statistics for the debug build.
by bitkarma 8y ago
I never did figure why the author insisted on reporting the runtime statistics for the debug build.
- scott_s 8y agoFrom the post: >One number that we haven’t moved substantially yet is the time it takes to run this code in debug using MSVC. While it’s natural to expect unoptimized builds to be slower than optimized, they have to be fast enough. Sometimes you want to debug your problem on a non-trivial input dataset. Sometimes you want to run the debug build with full checks through your tests to make sure they don’t trigger any bugs that could disappear in release. Sometimes you are trying to debug a different part of the program, but you still need to run the rest of it. The library, by the author, is https://github.com/zeux/meshoptimizer https://github.com/zeux/meshoptimizer. I presume it will be used in graphics pipelines. Debug builds working at a speed that allow graphics to be tolerable by humans sounds like a good goal to have.