[
https://issues.apache.org/jira/browse/FLINK-15318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127940#comment-17127940
]
Yun Tang commented on FLINK-15318:
----------------------------------
Since we already have the repo: [https://github.com/apache/flink-benchmarks], I
wonder the significance of those \{{RocksDB*PerformanceTest}}s and unit test
performance would easily be affected by the status of running host.
I prefer to remove them all: ({{RocksDBListStatePerformanceTest}},
{{RocksDBWriteBatchPerformanceTest}} and {{RocksDBPerformanceTest}}), and we
could also add cases in flink-benchmarks if we think some field is only covered
by those tests.
What do you think of this [~sewen], [~rmetzger]?
> 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)
