I have a question about how camel processes iterables - I've been trying
to track what looks like runaway memory usage. Based on thread
profiles we're not going nuts running everything in parallel so another
possibility that comes to mind is that the collection of items to be
worked on is getting pre-iterated over and messages are being queued up
in advance. We actually need certain things to run in parallel but be
limited by the available size of a threadpool so we might configure the
route to run 10 things in parallel but need to run a million things
through that route, just 10 at a time. Hopefully my question is
making sense.
