default logging to console has bad perf on windows, should be disabled by default

[Maoni0]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

this is without much logging and it's taking up 8.8% inclusive CPU. disabling colors didn't help. it's just really non performant to log to console on windows. please consider disabling this by default.

• Thread (10844) CPU=1886ms (Console logger queue processing thread) | 8.8 | 1,886
  |+ ntdll!RtlUserThreadStart | 8.5 | 1,836
  ||+ kernel32!BaseThreadInitThunk | 8.5 | 1,836
  || + coreclr!ThreadNative::KickOffThread | 8.5 | 1,836
  ||  + coreclr!ManagedThreadBase_DispatchOuter | 8.5 | 1,836
  ||   + coreclr!ManagedThreadBase_DispatchMiddle | 8.5 | 1,836
  ||    + coreclr!ThreadNative::KickOffThread_Worker | 8.5 | 1,836
  ||     + coreclr!DispatchCallSimple | 8.5 | 1,836
  ||      + coreclr!CallDescrWorkerInternal | 8.5 | 1,836
  ||       + system.private.corelib!System.Threading.Thread::StartCallback() | 8.5 | 1,836
  ||        + microsoft.extensions.logging.console!Microsoft.Extensions.Logging.Console.ConsoleLoggerProcessor::ProcessLogQueue() | 8.5 | 1,836
  ||         + Microsoft.Extensions.Logging.Console.il!AnsiParser.Parse | 5.1 | 1,106
  ||         |+ Microsoft.Extensions.Logging.Console.il!AnsiParsingLogConsole.WriteToConsole | 5.0 | 1,070
  ||         ||+ system.console.il!ConsolePal.set_BackgroundColor | 1.6 | 347
  ||         |||+ system.console.il!ConsolePal.GetBufferInfo | 1.6 | 345
  ||         ||||+ system.console.il!dynamicClass.IL_STUB_PInvoke(int,value class CONSOLE_SCREEN_BUFFER_INFO&) | 1.5 | 333

Expected Behavior

for something so non performant, should disable by default or change to another form of logging (ie to a file).

Steps To Reproduce

I have an internal app that I cannot share - if you can't repro feel free to let me know.

Exceptions (if any)

No response

.NET Version

.net 6

Anything else?

No response

[adityamandaleeka]

Spoke offline, apparently the reproducer is pretty much an MVC app that displays a bunch of messages in the console.

We should try to reproduce and investigate.

Thanks for contacting us.
We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Thanks for contacting us.
We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.