Debug WriteLine Performance Issues on Visual Studio 2017 with Rebuild

Question

My C# Web Forms and Web Applications require a LOT of System.Diagnostics.Debug.Writeline output. The applications processes a LOT of data (by a lot I mean a lot more than most people but a lot less than most significant commercial data apps) about 100s of MBytes or less.

I only use Visual Studio 2017 and C# SQL Server Express..and I'd like to continue to use them. However, upgrading to HPs i7 CPUs (either Spectre X360 or even the fastest CPUs DAMEN i7 OMEN 6 Core i8 CPUs), and doing a reinstall then slows the application testing/debuggin to an absolute crawl... it's not use-able. (Although processing not in Debug (Writeline output) is screaming fast)

So my next question is What IDE can I use to replace VISUAL STUDIO if I can not get this resolved very quickly? IMPORTANT NOTE: I have turned off literally every feature in MS VS2017 Tools --> Options that all Posts found have suggested still to no benefit.

Answer 1

The System.Diagnostics. Debug .Writeline method is quick way to output debugging data and should not be used in production or large output scenarios. Use the File class to output the data to a file, and write a separate Monitoring program to read and display the file as it changes.

Answer 2

For the record: Thanks @Stom for info -- in my case I do want fast test data.. (nothing else)... howevever I found the solution!!

To my surprise and amazement after trying every options in Tools -> Options -> Debug Etc Etc Etc and many others I found the ONE setting that is the most important for Debug Output using Multi Core processors (like more than 2) is :

Tools -> Options -> Projects and Solutions -> Build and Run -> X Maximum Number of Parallel Projects

Set this to the number of actual cores running on your CPU (ie .. likely not 12 as is default).

Whalaa... Debug Output 10000 x Faster.