You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gearpump.apache.org by "Manu Zhang (JIRA)" <ji...@apache.org> on 2017/10/17 15:12:00 UTC

[jira] [Commented] (GEARPUMP-358) Performance regression due to costly watermark calculation

    [ https://issues.apache.org/jira/browse/GEARPUMP-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207755#comment-16207755 ] 

Manu Zhang commented on GEARPUMP-358:
-------------------------------------

I don't think it's the message that has caused regression since we previously sent message to self as well. Nonetheless, we should avoid watermark calculation on each message. Maybe an update interval like that between TaskActor and ClockService will do ?

> Performance regression due to costly watermark calculation
> ----------------------------------------------------------
>
>                 Key: GEARPUMP-358
>                 URL: https://issues.apache.org/jira/browse/GEARPUMP-358
>             Project: Apache Gearpump
>          Issue Type: Bug
>            Reporter: Huafeng Wang
>
> For example, in streaming example SOL, everytime SOLStreamProducer output a message to downstream, it will send a Watermark message to itself, which will trigger watermark calculation. We should avoid flooding Watermark messages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)