Hi Ganesh, As Zhanghao Chen told before, He advise you two solutions for different scenarios.
1.Process record is a CPU-bound task: scale up parallelism of task and flink cluster to improve tps. 2.Process record is a IO-bound task: use Async-IO to reduce cost of resource and alse get better performance. Best, Zhongqiang Gong Ganesh Walse <ganesh.wa...@gmail.com> 于2024年3月29日周五 12:00写道： > You mean to say we can process 32767 records in parallel. And may I know > if this is the case then do we need to do anything for this. > > On Fri, 29 Mar 2024 at 8:08 AM, Zhanghao Chen <zhanghao.c...@outlook.com> > wrote: > >> Flink can be scaled up to a parallelism of 32767 at max. And if your >> record processing is mostly IO-bound, you can further boost the throughput >> via Async-IO [1]. >> >> [1] >> https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/operators/asyncio/ >> >> Best, >> Zhanghao Chen >> ------------------------------ >> *From:* Ganesh Walse <ganesh.wa...@gmail.com> >> *Sent:* Friday, March 29, 2024 4:48 >> *To:* user@flink.apache.org <user@flink.apache.org> >> *Subject:* One query just for curiosity >> >> Hi Team, >> If my 1 record gets processed in 1 second in a flink. Then what will be >> the best time taken to process 1000 records in flink using maximum >> parallelism. >> >
