I wasn’t expecting a bug report either :) Re the record stuff: I agree that the
schema handling can be a bit complicated when you’re getting started.
Especially if you’re not familiar with Avro and the schema format that it uses.
But typically once you create a couple of schemas and configure
Thanks Mark - I was not expecting a Bug report out of this! I'll give the
0 millis a try tomorrow and see what happens. In fairness, your laptop is
probably more powerful than the virtual CPUs I'm running on :-).
@Ryan I've got to learn the Record stuff better than I have now... It's the
whole
Hey Ryan,
I tried to replicate the behavior that you’re seeing. I wasn’t seeing behavior
as slow as what you’re mentioning, but was definitely seeing significantly
slower performance than I would have expected (reached about 1.5 million/5 mins
on my laptop, would expect about 8-10 million/5
Hi Ryan
I would merge the files into larger files before distribute load and use
PutElasticsearchHttpRecord
On Tue, Sep 15, 2020, 5:43 PM Ryan Hendrickson <
ryan.andrew.hendrick...@gmail.com> wrote:
> Hi Mark,
>I'm using Next Available, and the Destination Queues are set with Zero
> (0)
Hi Mark,
I'm using Next Available, and the Destination Queues are set with Zero
(0) for Back Pressure and Size threshold, so the destinations should not
fill up.
I did switch to using RoundRobin and set it to a yield of 0. That got
me up to about 300,000 ff's / 5 minutes. I was hoping for
Ryan,
I presume you’re using the Round Robin strategy? Looks like that strategy will
yield the processor if any destination is full. And it sounds like that will be
very common in your case. Would recommend configuring the Processor and in the
Settings tab, set the Yield Duration to “0 secs”.
