Irrespective of any providers configured, there have been occasional, rare cases of massive performance issues (reported from within the VSCode console, confirmation from a regular console would be welcome).
Stopping the logging runspace solves the performance hit, but disables logging:
Stop-PSFRunspace -Name 'psframework.logging'
When the issue occurs in a default code console, several phenomenon can be observed:
CPU Consumption spikes
Procmon finds massive numbers of file access to the logging folder in minimal time
Security Solution CPU consumption spikes
The only situation that covers this scenario would be the logging runspace ignoring the sleep statement at each logging cycle.
More investigation into when System.Threading.Thread.Sleep() does not actually do anything is needed.
Irrespective of any providers configured, there have been occasional, rare cases of massive performance issues (reported from within the VSCode console, confirmation from a regular console would be welcome).
Stopping the logging runspace solves the performance hit, but disables logging:
When the issue occurs in a default code console, several phenomenon can be observed:
Security Solution CPU consumption spikes
The only situation that covers this scenario would be the logging runspace ignoring the sleep statement at each logging cycle. More investigation into when
System.Threading.Thread.Sleep()does not actually do anything is needed.