Interestingly, threads are causing 5% increase mostly from unmarshal call
from openwire format but there is 20% increase in context switching
(vmstats). Profiler shows that all functions used for business logic/
processing (I mean functions of my program that were same before and after
AMQ implemen
On 08/15/2013 02:44 PM, zackhasit wrote:
Thanks. From looking at the profiler it looks like there are a lot more
threads running than before (6 threads per connection to broker) and most
increase might be context switching. Is it possible to reduce threads in
general to bare minimum.
As I see i
Thanks. From looking at the profiler it looks like there are a lot more
threads running than before (6 threads per connection to broker) and most
increase might be context switching. Is it possible to reduce threads in
general to bare minimum.
As I see it :
IOTranport thread
DedicatedTaskRunner
On 08/15/2013 02:00 PM, zackhasit wrote:
OK. I should mention that my program has taken code directly from simple
producer and simple consumer in the test program supplied with CMS code
(Since I am newbie it felt easiest way). The program get messages (like
simple consumer), does its own work and
OK. I should mention that my program has taken code directly from simple
producer and simple consumer in the test program supplied with CMS code
(Since I am newbie it felt easiest way). The program get messages (like
simple consumer), does its own work and send it to another broker (like
simple pro
On 08/15/2013 10:39 AM, zackhasit wrote:
Hi, I have an application that's using 20% more CPU after implementing CMS. I
was wondering if there was any way of reducing it. I am ok with reducing
functionality such as ACKs etc if that helps. There is no persistence
involved either. 5% of that increas
