It looks like the 'isRateLimited' flag was used on these tests inside google ~5 years ago, but I don't think we've ever used it in Beam. I don't believe there are any tests so it doesn't really surprise me that it is broken.
The configs we normally run nexmark on Flink with are here: https://github.com/apache/beam/blob/master/.test-infra/jenkins/job_PostCommit_Java_Nexmark_Flink.groovy On Thu, Jan 7, 2021 at 6:36 AM Teodor Spæren <teodor_spae...@riseup.net> wrote: > Hello and happy new years! > > I've been trying to use Nexmark for evaluating some performance > improvements I've made to Beam. I've discovered a problem where Nexmark > won't work if you enable the ratelimiting mode. I've filled out a bug > report for this[1]. > > To reproduce the problem is easy, simply run the normal nexmark suite > with ratelimiting mode enable and see that the number of results you get > is way lower than it should be. > > I've reached the limit of what I'm able to debug. Is this reproducible > for anyone else and does anyone have a clue about why this might happen? > > Any help is very much appreciated! > > Teodor > > [1]: https://issues.apache.org/jira/browse/BEAM-11547 >
