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 implementation and have nothing to do with AMQ as such) have increased CPU time significantly adding to another 15% increase. Even a call to new() now takes twice more CPU.
Note: System in general is 90% idle so plenty of CPU otherwise. -- View this message in context: http://activemq.2283324.n4.nabble.com/High-CPU-on-CMS-application-tp4670425p4670443.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
