ForkJoinPool.getActiveThreadCount() overestimating thread count
Why ForkJoinPool.getActiveThreadCount() can overestimate the number of
threads? While the ForkjoinPool itself doesnt describe the real reason, it
appears that the rest state of the computing thread (while waiting for the
forked one to join) may be causing it. Not sure why this occurs.
No comments:
Post a Comment