qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carl Trieloff <cctriel...@redhat.com>
Subject Re: Does --worker-threads option in broker improve performance
Date Mon, 03 Dec 2012 21:41:47 GMT


or if qpidd is pinned to socket, set it to the core count of the socket
+1. If you pin, pin to the second scocket, pin OS to core 0, socket 0.

If only one socket, set to core count +1

Carl.



On 12/02/2012 04:59 PM, Cliff Jansen wrote:
> The default varies from machine to machine and if N is the number of
> CPU threads that the operating system has available to it, the default
> is N+1.  This should get you close to the sweet spot, but as in all
> things performance related, your specific use case may benefit from
> more or fewer threads.  You would have to run your own representative
> benchmarks.  But if your cpu monitor is already showing you close to
> zero idle, increasing the worker threads will probably be
> counterproductive.
>
> Cliff
>
> On Sun, Dec 2, 2012 at 12:07 PM, Rajesh Khan <rajeshkhan808@gmail.com> wrote:
>> While going through the --help of Qpidd Broker I noticed --worker-threads
>> parameter. In the documentation of broker it states that this parameter is
>> used to set the thread pool size the default of which is 3. If I increase
>> this value will QPID perform better. Since I have 5-6 different
>> applications that run in parallel and continuously send messages to QPID
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message