Thanks for the comments. bq. I think the perf e2e test suites will also need to be designed as supporting running on both standalone env and distributed env. will be helpful for developing & evaluating the perf. Agreed and marked down, the benchmark will be able to be executed in standalone mode. On the other hand, we plan to check the result in distributed mode to better reflect network cost for the daily run.
Best Regards, Yu On Mon, 4 Nov 2019 at 10:00, OpenInx <open...@gmail.com> wrote: > > The test cases are written in java and scripts in python. We propose a > separate directory/module in parallel with flink-end-to-end-tests, with the > > name of flink-end-to-end-perf-tests. > > Glad to see that the newly introduced e2e test will be written in Java. > because I'm re-working on the existed e2e tests suites from BASH scripts > to Java test cases so that we can support more external system , such as > running the testing job on yarn+flink, docker+flink, standalone+flink, > distributed kafka cluster etc. > BTW, I think the perf e2e test suites will also need to be designed as > supporting running on both standalone env and distributed env. will be > helpful > for developing & evaluating the perf. > Thanks. > > On Mon, Nov 4, 2019 at 9:31 AM aihua li <liaihua1...@gmail.com> wrote: > > > In stage1, the checkpoint mode isn't disabled,and uses heap as the > > statebackend. > > I think there should be some special scenarios to test checkpoint and > > statebackend, which will be discussed and added in the release-1.11 > > > > > 在 2019年11月2日，上午12:13，Yun Tang <myas...@live.com> 写道： > > > > > > By the way, do you think it's worthy to add a checkpoint mode which > just > > disable checkpoint to run end-to-end jobs? And when will stage2 and > stage3 > > be discussed in more details? > > > > >
