Re: Flink CEP Resource Utilisation Optimisation

2023-03-27 Thread Abhishek Singla
> *发送时间:* Monday, March 27, 2023 12:38:59 AM >> *收件人:* Geng Biao >> *抄送:* user@flink.apache.org >> *主题:* Re: Flink CEP Resource Utilisation Optimisation >> >> Thanks, Geng for the quick and actionable response. >> >> I will definitely try this with Flink v

Re: Flink CEP Resource Utilisation Optimisation

2023-03-26 Thread Abhishek Singla
- > *发件人:* Abhishek Singla > *发送时间:* Monday, March 27, 2023 12:38:59 AM > *收件人:* Geng Biao > *抄送:* user@flink.apache.org > *主题:* Re: Flink CEP Resource Utilisation Optimisation > > Thanks, Geng for the quick and actionable response. > > I wil

Re: Flink CEP Resource Utilisation Optimisation

2023-03-26 Thread Geng Biao
. Best, Biao 获取 Outlook for iOS<https://aka.ms/o0ukef> 发件人: Abhishek Singla 发送时间: Monday, March 27, 2023 12:38:59 AM 收件人: Geng Biao 抄送: user@flink.apache.org 主题: Re: Flink CEP Resource Utilisation Optimisation Thanks, Geng for the quick and actionable respon

Re: Flink CEP Resource Utilisation Optimisation

2023-03-26 Thread Abhishek Singla
n there are > no new partial matched and CEP Operator will not use more state. > > > > Best, > Biao Geng > > > > *From: *Abhishek Singla > *Date: *Sunday, March 26, 2023 at 11:58 PM > *To: *user@flink.apache.org > *Subject: *Flink CEP Resource Utilisation Opti

Re: Flink CEP Resource Utilisation Optimisation

2023-03-26 Thread Geng Biao
ate matching result in the state. So if there are no new events, then there are no new partial matched and CEP Operator will not use more state. Best, Biao Geng From: Abhishek Singla Date: Sunday, March 26, 2023 at 11:58 PM To: user@flink.apache.org Subject: Flink CEP Resource Utilisation Opt

Re: Flink CEP Resource Utilisation Optimisation

2023-03-26 Thread simple
退订 发自我的iPhone -- Original -- From: Abhishek Singla

Flink CEP Resource Utilisation Optimisation

2023-03-26 Thread Abhishek Singla
Hi Team, *Flink Version:* 1.15.0 *Java Version:* 1.8 *Standalone Cluster* *Task Manager:* AWS EC2 of Instance Type c5n.4xlarge (vCPU 16, Memory 42 Gb, 8 slots per TM) *CEP Scenario:* Kafka Event A followed by Kafka Event B within 10 mins *Throughput:* 20k events per second for Event A, 0 for Kafka