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

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

GitHub user sandeshh opened a pull request:

    https://github.com/apache/incubator-apex-core/pull/287

    apexcore-407 adaptive spin millis for input operators

    I tested change with the benchmarking and I can clearly see the improvement 
in performance. It is similar to what was done before
    
    https://issues.apache.org/jira/browse/APEXCORE-380
    https://github.com/apache/incubator-apex-core/pull/271
    
    Performance numbers increased from <710000 tuples/sec to >10,00,000 
tuples/sec.
    
    This change was reviewed by @vrozov, closed the old one as Travis build was 
failing. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sandeshh/incubator-apex-core 
apexcore-407-squash

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-apex-core/pull/287.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #287
    
----
commit 062c01ae6e0bdc00801d7978a1a9774f98398d73
Author: sandeshh <[email protected]>
Date:   2016-03-28T18:19:45Z

    apexcore-407 adaptive spin millis for input operators
    
    changed the order of sleep

----


> Idle time sleep time should increase from 0 to a configurable max value
> -----------------------------------------------------------------------
>
>                 Key: APEXCORE-380
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-380
>             Project: Apache Apex Core
>          Issue Type: Improvement
>    Affects Versions: 3.4.0
>            Reporter: Vlad Rozov
>            Assignee: Vlad Rozov
>             Fix For: 3.4.0
>
>
> When all active input ports of an operator are empty, the operator either 
> calls idle time handler or goes into a wait. In the later case, the wait time 
> should start with 0 and increase to the configured/default idle spin time to 
> handle cases when there is trickle and pour stream of tuples.



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

Reply via email to