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 when data is available too.
On Sat, Aug 3, 2019 at 10:18 AM [email protected] < [email protected]> wrote: > > 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 this? > ------------------------------ > [email protected] > > > *发件人：* [email protected] > *发送时间：* 2019-08-02 15:25 > *收件人：* users <[email protected]> > *主题：* Does CaptureChangeMySQL processor is CPU intensive? > > I just run a single CaptureChangeMySQL processor， the cpu usage is more > than 100% > > Is it normal? > If so, why it is so cpu intensive? > > > > ------------------------------ > [email protected] > > -- Sent from Gmail Mobile
