I only looked at this quickly, but I think the queue.poll in the onTrigger
method should use a small blocking time of about 10ms so that when no
events are available it won’t crush the CPU. Right now you could change the
scheduling of the processor from 0 seconds to 10ms but then that slows it
down
Many thanks for the valuable feedback.
On Fri, Aug 2, 2019 at 8:50 AM Edward Armes wrote:
> HI Clay,
>
> So as Bryan has said the actual connection is managed by a selector and
> all this does is goes through each connection and once that connection has
> data to receive it the selector then han
First I set the binlog position to a earlier value, the processor takes about
20% cpu usage and consumes binlog much faster than what is generated.
But after it catched up with the latest binlog postion, the cpu usage go up to
about 200%.
I have no idea why this happens.
Any insight on thi
First I set the binlog position to a earlier value, the processor takes about
20% cpu usage and consumes binlog much faster than what is generated.
But after it catched up with the latest binlog postion, the cpu usage go up to
about 200%.
I have no idea why this happens.
Any insight on thi
