apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-201) Reported latency is wrong when a downstream operator is behind more than 1000 windows
Date Fri, 19 Feb 2016 01:01:31 GMT

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

ASF GitHub Bot commented on APEXCORE-201:
-----------------------------------------

Github user davidyan74 commented on the pull request:

    https://github.com/apache/incubator-apex-core/pull/230#issuecomment-185999278
  
    This PR is different from #194:
    - critical path calculation no longer visits the same nodes twice
    - critical path calculation now takes care of delay loops
    
    @tweise @PramodSSImmaneni please review
    @gauravgopi123 I implemented the optimization you mentioned last time


> Reported latency is wrong when a downstream operator is behind more than 1000 windows
> -------------------------------------------------------------------------------------
>
>                 Key: APEXCORE-201
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-201
>             Project: Apache Apex Core
>          Issue Type: Bug
>            Reporter: David Yan
>            Assignee: David Yan
>
> We should probably estimate this by reporting the latency using the number of windows
behind when that happens.  Right now it reports a stale latency.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message