Salut,
Bongjae Chang wrote:
> Hi,
>
> I saw your comment.
>
> Jeanfrancois wrote:
> >Once applied, I will go ahead and ask internally for performance testing.
>
> At present, I tried to test PipelineThreadPool's performance curiously.
>
> I just tested only PipelineThreadPool without grizzly's dependency simply.
>
> I could know that LinkedTransferQueue had an big effect on performace.
>
> When I changed the LinkedTransferQueue into ArrayBlockingQueue or
> another BlockingQueue which had special queue size, I could find that
> the performance was improved seriously.
>
> Most of PipelineThreadPool's constructors set default
> LinkedTransferQueue. So, I am curious to know why LinkedTransferQueue
> was made on purpose.
This is coming from Doug Lea workspace and we were told they where
faster. How did you test it? I'm all for reverting back to use
LinkedTransferQueue if it perform better as we don't have to manage the
code ourself.
Thanks!
-- Jeanfrancois
>
> FYI.
>
> Thanks!
>
> --
> Bongjae Chang
>
>