Todd C. Gleason
2003-08-08 22:47:26 UTC
I am running a mixed-mode set of projects under Visual
Studio .NET 2003 (7.1.3088, .NET 1.1.4322):
MFC-based C++ GUI
C# DLLs
Managed C++ DLLs
For some reason, the debugger's output window causes a
huge amount of slowdown. Either using the MFC TRACE
macro, or Debug.WriteLine, it is quite slow. I get maybe
10 lines max written out in a single second. I even
tried writing lines in a tight loop, and it was
definitely slowing down for just the output window. This
performance is probably 10% of what VC++ 6.0 had.
It doesn't eat up the CPU, either. I looked in the task
manager and it's being slow at a mere 10% CPU or so. I
removed the TRACE statements and my code executes like
lightning (proving that, hey, managed code runs fast).
Still, I'd like to have my trace output back. I talked
to a coworker, who is working on pure C# (totally
different code base, using the 2002 edition), and she
thinks she may be experiencing similar problems.
I haven't noticed any posts about this problem--can
anyone confirm?
Studio .NET 2003 (7.1.3088, .NET 1.1.4322):
MFC-based C++ GUI
C# DLLs
Managed C++ DLLs
For some reason, the debugger's output window causes a
huge amount of slowdown. Either using the MFC TRACE
macro, or Debug.WriteLine, it is quite slow. I get maybe
10 lines max written out in a single second. I even
tried writing lines in a tight loop, and it was
definitely slowing down for just the output window. This
performance is probably 10% of what VC++ 6.0 had.
It doesn't eat up the CPU, either. I looked in the task
manager and it's being slow at a mere 10% CPU or so. I
removed the TRACE statements and my code executes like
lightning (proving that, hey, managed code runs fast).
Still, I'd like to have my trace output back. I talked
to a coworker, who is working on pure C# (totally
different code base, using the 2002 edition), and she
thinks she may be experiencing similar problems.
I haven't noticed any posts about this problem--can
anyone confirm?