[
https://issues.apache.org/jira/browse/FLINK-15104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991243#comment-16991243
]
Piotr Nowojski commented on FLINK-15104:
----------------------------------------
I'm not sure about that [~liyu]. We can wait for FLINK-15103 to be addressed,
but both of those benchmarks mentioned in this ticket description suggests that
another independent performance happened somewhere in the commit range
{{e505bef..36cb5d4}}, which is one full day later compared to FLINK-15103.
Keep in mind that the other state backend benchmarks are operating on lower
layer so they might quite have different test coverage compared to those two
stateBackends.ROCKS(_INC) job level benchmarks.
> 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)
