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
Thanks for the great tool. I'm of the opinion that Kleborate should not use more than 1 thread unless allocated more via a command line arg as I suppose it would be possible for it to clobber hundreds of CPUs in a worst case scenario without the user being able to control it.
Is it possible limit to 1 thread by default and add a flag when calling the tool if the user wants more? I don't expect that multithreading would provide significant speed advantage regardless?
The text was updated successfully, but these errors were encountered:
Thanks for the great tool. I'm of the opinion that Kleborate should not use more than 1 thread unless allocated more via a command line arg as I suppose it would be possible for it to clobber hundreds of CPUs in a worst case scenario without the user being able to control it.
I see this in the code:
Kleborate/kleborate/kaptive.py
Lines 53 to 68 in f2c9c31
Is it possible limit to 1 thread by default and add a flag when calling the tool if the user wants more? I don't expect that multithreading would provide significant speed advantage regardless?
The text was updated successfully, but these errors were encountered: