Re: Speed optimization of Spliterators.spliteratorUnknownSize for parallel case

2015-07-15 Thread Paul Sandoz
On Jul 15, 2015, at 2:20 PM, Paul Sandoz wrote: >> By the way currently it's possible to create an IteratorSpliterator >> with estimated size: >> >> Spliterators.spliterator(iterator, estimatedSize, Spliterator.CONCURRENT); >> >> Of course it's a misuse of CONCURRENT flag, but it's not used >> o

Re: Speed optimization of Spliterators.spliteratorUnknownSize for parallel case

2015-07-15 Thread Paul Sandoz
Hi Tagir, On Jul 14, 2015, at 4:43 AM, Tagir F. Valeev wrote: > Hello! > > Thank you for the detailed answer. > > PS> Thanks for looking at this. Judging by the results i am guessing > PS> your measurements were performed on a 4-core system. > > Yes, quad-core, I mentioned it before. > > PS>

Re: Speed optimization of Spliterators.spliteratorUnknownSize for parallel case

2015-07-13 Thread Paul Sandoz
Hi Tagir, Thanks for looking at this. Judging by the results i am guessing your measurements were performed on a 4-core system. My initial inclination for these scenarios is it is likely better for the developer to split the execution in two parts. The first part, low N and low Q, is to collec