misc catchup

[Aleksey Shipilev]

On 10/30/2012 09:49 PM, Brian Goetz wrote:
>> As most of you probably probably surmised from
>>  http://cs.oswego.edu/pipermail/concurrency-interest/2012-October/010182.html
>> implicit use of the ForkJoinPool.commonPool can/should replace
>> the internal ForkJoinUtils in lambda builds. Besides being easier
>> to use, and reducing resource use when people are otherwise
>> tempted to create their own "default" pools, it exploits knowledge
>> of the pool to improve execution times, In particular, fjt.invoke()
>> will often be faster than FJP.invoke(fjt); moreso when people use
>> some new idioms (including those I've thought of and probably more.)
> 
> As soon as we have this merged, we'll migrate our implementation.  

It's actually there in my patch on lambda-dev at . I had dumped the parts
already implemented in FJP from ForkJoinUtils, as well as translate our
usages of FJP.invoke(fjt) to fjt.invoke(), plus translating tryCompleter
-> helpCompleter. You might want to review that patch more thoroughly,
but the wakeup performance is clearly better.

-Aleksey.