[
https://issues.apache.org/jira/browse/FLINK-15318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002716#comment-17002716
]
Yun Tang commented on FLINK-15318:
----------------------------------
[~siddheshghadi] I noticed that you also come across that in release-1.8 which
is an older version of FRocksDB. From my previous experience, I have noticed
that FRocksDB on ppc64le platform behaves worse than other platforms and I
actually have not met some guys using Flink in production with ppc64le
environment.
In a nut shell, the timeout for FRocksDB is not enough on ppc64le platform. Did
you use Flink in production on ppc64le platform? I am afraid Flink community
lacks of rich experience on ppc64le especially for FRocksDB performance. By the
way, can you try to use RocksDB instead of FRocksDB to run the tests (Remember
to remove all the usage of {{org.rocksdb.FlinkCompactionFilter}} so that you
could build with official RocksDB).
> 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)
