We are noticing significant performance degradation with persistence
turned on, when the no of concurrent users is more than 50. Our
application(which is like is SOA Framework) is using active 4.1 running on
Linux Redhat with 2 Cores, 8GB Ram and using SAN for journal files storage.
Our current setup has our application running on one Linux Server and Active
MQ is running on second server( both servers have identical memory and
processors).
I tried all the persistence options like jounaledjdbc with mysql,
jdbc with mysql, kaha, but didnot see any improvements. To isolate any
application related issues, we tried commericial MQ's like Tibco EMS and
sonic and we didn't see any substantial degradation.
Currently our framework creates connection, session and producer
during startup and is also using single producer to send messages to
multiple destinations. Also we are using AUTO_ACKNOWLEGE mode with prefetch
=1.Once i change this to create session,producer on the fly for each request
we saw some improvements. This is serious roadblock and could potentially
force our management to move away from activeMQ. I would appreciate if any
activeMQ folk help us out with this issue
--
View this message in context:
http://www.nabble.com/Please-help%3A-Performance-issue-with-persistence-tf3345502s2354.html#a9304224
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
