[
https://issues.apache.org/jira/browse/FLINK-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625255#comment-14625255
]
ASF GitHub Bot commented on FLINK-1967:
---------------------------------------
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/906#issuecomment-121040843
These are the results of my performance tests:
https://docs.google.com/spreadsheets/d/1mXcy25UOiZ4lEJOia1OM-K-U6np2bWv3x4q5nSnUMdg/edit?usp=sharing
Some numbers are maybe a bit inaccurate because I only gave it 6 minutes of
runtime for every test configuration. Especially, with the watermark intervals,
sometimes the throughput is better for a lower watermark interval. This seems
counterintuitive but I think the performance can differ quite a bit between
runs, I think @rmetzger has also seen this behavior.
> Introduce (Event)time in Streaming
> ----------------------------------
>
> Key: FLINK-1967
> URL: https://issues.apache.org/jira/browse/FLINK-1967
> Project: Flink
> Issue Type: Improvement
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
>
> This requires introducing a timestamp in streaming record and a change in the
> sources to add timestamps to records. This will also introduce punctuations
> (or low watermarks) to allow windows to work correctly on unordered,
> timestamped input data. In the process of this, the windowing subsystem also
> needs to be adapted to use the punctuations. Furthermore, all operators need
> to be made aware of punctuations and correctly forward them. Then, a new
> operator must be introduced to to allow modification of timestamps.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
