(This was previously included in some "miscellaneous" changes picked up in https://bugs.openjdk.java.net/browse/JDK-8214559CR but now broken out separately after backout and resubmission.)

ForkJoinPool intrinsically oversignals possibly-needed worker threads, but signalling too many workers causes overhead and contention. This oversignalling can be reduced while maintaining liveness.