boday wrote:
>
> Alright now that I'm getting better througput to my AMQ queue from HTTP
> (~600/second), the next bottleneck is in my process that parses the
> inbound message (simple Java XML parsing and validation) and publishes it
> to a topic.
>
> from("activemq:GatewayMsgQueue")
> .process(new MessageProcessor())
> .to("activemq:topic:PortalTopic");
>
> Using a single queue consumer, the MessageProcessor is able to handle
> about 100 messages/second. My GatewayMsgQueue simply backs up at the rate
> of about 500 msg/second.
>
> I thought that I simply needed to increase the number of concurrent
> consumers, but that hasn't seemed to make a difference in overall
> throughput either.
>
> from("activemq:GatewayMsgQueue?maxConcurrentConsumers=10")
> .process(new MessageProcessor())
> .to("activemq:topic:PortalTopic");
>
> I also tried adding an explicit thread statement to help things along...is
> this any different?
>
> from("activemq:GatewayMsgQueue")
> .thread(10)
> .process(new MessageProcessor())
> .to("activemq:topic:PortalTopic");
>
> No luck with either approach...my overall throughput remains the same.
> Any other ideas what would make this route yield a higher throughput? I'm
> working on a dual core CPU, I'd think the concurrent consumer approach
> would help a bit at least.
>
> thanks
>
>
>
>
>
The option is named: concurrentConsumers
the max one will just be like an upper bounds. So use concurrentConsumers=10
to use 10 at the same time.
And also notice the bad defaults about maxMessagesPerTask that is displayed
on top of this page
http://camel.apache.org/jms.html
--
View this message in context:
http://www.nabble.com/Camel-throughput-issues...HTTP-to-AMQ-tp24648117p24698014.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
