oakmound/oak

can debug console be disabled? (using lots of CPU)

Closed this issue · 4 comments

I was still seeing alot of high CPU use under idle conditions, so I profiled again and I see that even when idle, the debug console is chewing through alot of cpu. Is there any means (or harm) to shut it off?

image

200sc commented

We can certainly add a flag, but I would be really surprised if something waiting on stdin was eating CPU.

200sc commented

The upcoming release should add the configuration to disable the console input.

200sc commented

Flag added, merged and tagged. Feel free to reopen if there's a bug with the implementation.

Thanks Patrick!