[
https://issues.apache.org/jira/browse/FLINK-12818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913989#comment-16913989
]
Haibo Sun commented on FLINK-12818:
-----------------------------------
{quote}Alternatively until this is confirmed as a production code issue, we can
just try to live with this benchmark instability and relay on long term trends.
{quote}
+1. I think we can adopt this way first.
{quote}I think if we want to investigate this further, we would need to print
compiled byte code and try to understand the difference.
{quote}
I agree. I'll try when I have time.
> Improve stability of twoInputMapSink benchmark
> ----------------------------------------------
>
> Key: FLINK-12818
> URL: https://issues.apache.org/jira/browse/FLINK-12818
> Project: Flink
> Issue Type: Sub-task
> Components: Benchmarks
> Reporter: Piotr Nowojski
> Priority: Critical
> Attachments: RecordWriter-emit.png
>
>
> The {{twoInputMapSink}} benchmark is very unstable over time:
> http://codespeed.dak8s.net:8000/timeline/#/?exe=1&ben=twoInputMapSink&env=2&revs=200&equid=off&quarts=on&extr=on
> It should be fixed, otherwise the benchmark can not be used.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
