I'm not quite sure what you are attempting to do here.  You poll every 30
seconds and seem to only want to pick up 1 file but then say you want it to
pick up a "large amount of files every poll".  Are you trying to pick up
just 1 file every 30 seconds or are you trying to read all the files when
the poll fires?  If you want to pick up everything it will do that
normally.  Are you unmarshaling these files at some point? Speeding things
up can be accomplished via thread pools and getting them off the file
reader can be accomplished by something as simple as a SEDA queue with a
thread pool.  But you also have to be aware of how much data you have in
each file and make sure it doesn't exceed your memory settings.  That
usually means tremendously big files because folks usually overestimate how
much data a file represents.

"thinking  that the file component will pick up a single file every 30 secs
but it seems to consume the files like normal. Any idea why is it doing that
or am i doing something wrong? My idea is to use the maxMessagesPerPoll to
make the file component pick up a large amount of files every poll. Is that
going to speed up the consumption?"

On Fri, Oct 14, 2016 at 3:48 AM, redpower1989 <redpower1...@hotmail.com>

> I tried maxMessagesPerPoll = 1 and delay 30 secs and it wasn't picking 1
> file
> every 30 secs and i am wondering if i am setting something wrong on the
> consumer.
> By the way i found a way to speed up the file processing and it is the use
> of threads. Be careful that you need to find a balance for the poolsize
> value.
> http://camel.apache.org/async.html
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/file-component-polling-files-tp5788570p5788775.html
> Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to