[
https://issues.apache.org/jira/browse/FLINK-15318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136697#comment-17136697
]
Stephan Ewen commented on FLINK-15318:
--------------------------------------
The purpose of this test is to guard against the "quadratic concatenation
complexity bug" that RocksDB had a few versions ago.
In that case, the benchmark took 50s or so. We can probably increase this to 5s
without a problem.
How about this?
- we add it to the benchmarks suite to monitor regressions more precisely
- we keep it in the codebase with a timeout of 5 seconds or so, as a rough
guard
> RocksDBWriteBatchPerformanceTest.benchMark fails on ppc64le
> -----------------------------------------------------------
>
> Key: FLINK-15318
> URL: https://issues.apache.org/jira/browse/FLINK-15318
> Project: Flink
> Issue Type: Bug
> Components: Benchmarks, Runtime / State Backends
> Environment: arch: ppc64le
> os: rhel7.6, ubuntu 18.04
> jdk: 8, 11
> mvn: 3.3.9, 3.6.2
> Reporter: Siddhesh Ghadi
> Priority: Major
> Attachments: surefire-report.txt
>
>
> RocksDBWriteBatchPerformanceTest.benchMark fails due to TestTimedOut, however
> when test-timeout is increased from 2s to 5s in
> org/apache/flink/contrib/streaming/state/benchmark/RocksDBWriteBatchPerformanceTest.java:75,
> it passes. Is this acceptable solution?
> Note: Tests are ran inside a container.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
