http://bugs.winehq.org/show_bug.cgi?id=28604
--- Comment #10 from Yuri Khan yurivkhan@gmail.com 2011-11-20 02:44:50 CST --- Sadly, no noticeable effect on productivity. Rendering the same map extent (266K pixels, 16658 lines) twice on program startup seems to take 105 s in bres_line_with_bias on 1.3.33, 106s in solid_line_32 on 1.3.33 with patch. Measuring with a stopwatch, I get 3 minutes since I click the Next button on the startup screen until the CPU meter drops to near zero.
Maybe my measurements are not quite sound because of timer accuracy. Here’s how I do it. At the top of function to profile, I add this:
static DWORD time_total = 0, length_total = 0; DWORD time_once = GetTickCount(), length_once = /*suitable code*/;
At the end:
time_once = GetTickCount() - time_once; time_total += time_once; length_total += length_once; TRACE_(dib_profile)("Spent %d ms for %d px, total %d ms for %d px\n", time_once, length_once, time_total, length_total);
and run with WINEDEBUG=+dib_profile, redirecting all output to a file. The resulting file has many lines with spent time = 0 ms and some lines where spent time is about 45 ms. I assume it all statistically adds up to roughly the correct total in the end.