I can't compromise my business logic and there is hardly any data; but each
time camel Route 2 starts Route 1, the previous route processing goes onto
stack. I only have limited stack after that any operation can fail.
To me below approach seems risky...I need to go async or remove the looping out
of the route overall.
From: souciance [mailto:souciance.eqdam.ras...@gmail.com]
Sent: Thursday, October 13, 2016 3:45 PM
Subject: Re: Looping in routes using Direct Component - Performance impact?
I think you should first run your route setup with a few pages, 10s of
pages, hundreds of pages and then thousands of pages and then do
performance tests to see where what is eating memory and optimise from
On Fri, Oct 14, 2016 at 12:31 AM, Goyal, Arpit [via Camel] <
> We currently are on 2.16.3 version and can't use the loop function (part
> of 2.17). So we have the following routes based on which we create sort of
> loop with switch case. Now we are worried about the performance (when we
> see stacktrace of camel processing)
> Route 1: from("direct:s1).to("read one page of data").process("process
> one page").to("direct:s2");
> Route 2: from("direct:s2").toD("go to external source").when("are more
> pages left").to("direct:s1").otherwise().process("end processing");
> Now if there are thousands of pages, it is possible that this loop creates
> lot of objects in memory & can create performance issue? Is there a way for
> Camel to be told, before going to route 1 again, forget all the past? Is
> disabling HISTORY would solve that?
> If you reply to this email, your message will be added to the discussion
> To start a new topic under Camel - Users, email
> To unsubscribe from Camel - Users, click here
View this message in context:
Sent from the Camel - Users mailing list archive at Nabble.com.