From: Bongjae Chang <carryel_at_korea.com>
Date: Wed, 27 May 2009 22:15:41 +0900

Hi Alexey,

I agree with your words and [1] is very interesting!

So, I will attach my test code on tomorrow morning after investigating and verifying my test again.

Thanks.

--
Bongjae Chang


  ----- Original Message -----
  From: Oleksiy Stashok
  To: dev_at_grizzly.dev.java.net
  Sent: Wednesday, May 27, 2009 7:17 PM
  Subject: Re: About issue #623(PipelineThreadPool)'s performance testing


  Hi,



    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.
  Thank you for the investigation.
  IMHO, results could depend much on environment, where tests are running, and specific scenario. Because developer, who made that switch to LTQ, also spent some time on investigating the performance [1].
  Can you pls. share the testing environment and code?


  Thank you.


  WBR,
  Alexey.


  [1] http://www.nabble.com/2x-improved-instance-caching-throughput-td21460586.html#a21460586



    FYI.

    Thanks!

    --
    Bongjae Chang