You might be surprised, Carl. I was. Notice the highlighted difference in the thousandths times.
My quick-and-dirty test code uses SQL to fill the queue. Then I start a timer when I start reading through the queue (and outputting to debug) .
I’ll see if I can find time to extract the code into something standalone later today, if you’re interested.
jf
Wow! if I’m seeing this right old Debug View is 6.5 times slower than the new ++ Viewer (6273 / 967).
It makes sense the new code is has been optimized to be faster than the original from 1998.
Thanks Jane. I don’t need your code.
Carl, have you tried your code that checks for DBWIN_BUFFER_READY in the CW debugger? Because debuggers work differently I suspect you’ll find that you don’t get OutputDebugString() messages even when you’re debugging. Which may or not be important, but I thought it worth mentioning.
