[
https://issues.apache.org/jira/browse/FLINK-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626042#comment-14626042
]
ASF GitHub Bot commented on FLINK-1967:
---------------------------------------
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/906#issuecomment-121168918
The job I ran was source -> repartition -> sink, where the source is
generating tuples in an infinite loop.
The gist of the data is this (I'm rerunning some of them with longer
runtimes to remove outliers):
- Introducing timestamp for each record that is set at source incurs about
a 15 % performance hit in these tests
- Watermarks have no additional overhead once the interval is higher than
100 sec (I didn't test with lower intervals, such as 50 sec, but I will do
these today.)
> 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)
