flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dian Fu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-8106) Optimize the timer logic in AbstractKeyedCEPPatternOperator
Date Mon, 20 Nov 2017 08:20:00 GMT
Dian Fu created FLINK-8106:

             Summary: Optimize the timer logic in AbstractKeyedCEPPatternOperator
                 Key: FLINK-8106
                 URL: https://issues.apache.org/jira/browse/FLINK-8106
             Project: Flink
          Issue Type: Bug
          Components: CEP
            Reporter: Dian Fu
            Assignee: Dian Fu

Currently the logic of {{AbstractKeyedCEPPatternOperator}} is as follows when event time enabled:
1) When element comes, buffer it in {{MapState}} and and register a timer at {{watermark +
2) When event timer triggered, scan the {{MapState}} and find the elements below current watermark
and process it. If there are remaining elements to process or the NFA is not empty, register
a new timer at {{watermark + 1}}.

Let's assume that watermark comes about 5 seconds later than the event on average, then we
will scan about 5000 times the {{MapState}} before processing the events. We find that most
of the cpu is wasted serialization and deserialization the {{MapState}} when profiling an
CEP use case. After make the optimization of the timer logic, the through put increases from
10+ tps to about 3500 tps for one operator.

This message was sent by Atlassian JIRA

View raw message