You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could very well be my usage of bat-test being incorrect but I have some code where (bat-test) is called and then that's invoked from a boot-test, when I run VisualVM on that boot process this section appears to take a fair amount of CPU:
Since we point bat-test at all our tests anyway I don't think this section of code is doing much for us? Is it possible to optionally disable or avoid it?
The text was updated successfully, but these errors were encountered:
If VIsualVM is writes to app standard input it would explain why it takes lost of CPU time. If not, it is just overhead from the debugger, but that seems unlikely, as the read call in the loop should be just blocking until there is more input to read.
I tried to check java.util.Scanner implementation and looks like it isn't doing anything else that just reading System.in. Though difference is that it is reading input into CharBuffer and then handling all read bytes, instead of calling read for one byte at a time. That might be more efficient in a case where lots of stuff is written to std in.
But makes sense to just have option to disable this.
This could very well be my usage of bat-test being incorrect but I have some code where (bat-test) is called and then that's invoked from a boot-test, when I run VisualVM on that boot process this section appears to take a fair amount of CPU:
https://github.com/metosin/bat-test/blob/master/src/metosin/bat_test/impl.clj#L18
Since we point bat-test at all our tests anyway I don't think this section of code is doing much for us? Is it possible to optionally disable or avoid it?
The text was updated successfully, but these errors were encountered: