[
https://issues.apache.org/jira/browse/FLINK-15104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991115#comment-16991115
]
Yu Li commented on FLINK-15104:
-------------------------------
We checked against state-benchmark before releasing new frocksdb version and
confirmed there's no regression (result
[here|https://issues.apache.org/jira/browse/FLINK-14483?focusedCommentId=16980002&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16980002]),
and from the [latest state-benchmark
result|http://codespeed.dak8s.net:8000/timeline/#/?exe=3&ben=grid&env=2&revs=200&equid=off&quarts=on&extr=on]
on our speed center the result remains.
Based on the above facts, plus the benchmark of {{stateBackends.ROCKS}} is in
job mode, my guess is that the regression is caused by the same reason of
FLINK-15103 rather than bumping RocksDB version.
> Performance regression on 4.12.2019 in RocksDB benchmarks
> ---------------------------------------------------------
>
> Key: FLINK-15104
> URL: https://issues.apache.org/jira/browse/FLINK-15104
> Project: Flink
> Issue Type: Bug
> Components: Benchmarks, Runtime / State Backends
> Reporter: Piotr Nowojski
> Priority: Blocker
> Fix For: 1.10.0
>
>
> A potential small performance regression that happened either on December 4th
> or 5th:
> http://codespeed.dak8s.net:8000/timeline/?ben=stateBackends.ROCKS&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=stateBackends.ROCKS_INC&env=2
> it doesn't seem to be visible in the states benchmarks suites, which might be
> an issue on its own.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
