On Mon, Nov 4, 2013 at 11:53 AM, Ephemeris Lappis <[email protected]> wrote: > Hello. > > I exactly want to do what you say, "even out" the processing of my messages > and ensure a regular output for the target system, for example, about 1000 > calls per second. > > I hoped the throtller could help to do that, but it doesn't actually produce > a "smooth" output flow, but instead it blocks for the given period and > ejects a batch of data. >
Yeah IMHO we should add such functionality in the future to Camel throttler. So you can decide if you want current behavior or an "even out spread approximation" > I have no experience with route policies. Do you mean that the > "ThrottlingInflightRoutePolicy" may be a possible "out of the box" solution > for me ? > Yeah the inflight route policy will suspend/resume on the consumer side, so its more ideal if the consumer is a JMS queue etc. Then it can even out the spread as it has high/low watermarks it uses as triggers when to suspend/resume. > If it doesn't, what should be the best way to replace the default > "<throttle>" with a more "regular" one ? > You can build a custom java bean with the logic. Or a Camel processor extending the Camel throttler etc to reuse some of the code. > Thanks a lot. > > Best regards. > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/Camel-Throttle-linear-regulation-tp5718280p5718293.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
