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

ASF subversion and git services commented on ASTERIXDB-3628:
------------------------------------------------------------

Commit 7285518ca0d7492c7393ed906cb2fe041aaf714a in asterixdb's branch 
refs/heads/master from Ian Maxon
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=7285518ca0 ]

[ASTERIXDB-3628][RT] Correct subplan profiles

- user model changes: no
- storage format changes: no
- interface changes: no

Details:

Currently subplan timing information is calculated during close().
This can lead to inaccuracies in the timing, especially when the
subplan is near the end of a task pipeline, because other
operator's times are calculated after close, during deinitialize().

Correct this by adding the capability in the MetaOperator to invoke a
method on each ProfiledPushRuntime SubplanPushRuntime to calculate the
timings, so it can be invoked at the proper time as to retrieve the
correct time from its downstream operators.

Ext-ref: MB-67499

Change-Id: I4d38710626778ef52abb1cd4fe1e0b26e0d74bec
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/20069
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Ali Alsuliman <ali.al.solai...@gmail.com>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>


> Subplan profile timings not calculated correctly
> ------------------------------------------------
>
>                 Key: ASTERIXDB-3628
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3628
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: RT - Runtime
>    Affects Versions: 0.9.10
>            Reporter: Ian Maxon
>            Assignee: Ian Maxon
>            Priority: Major
>              Labels: triaged
>             Fix For: 0.9.10
>
>
> Currently subplan timing information is calculated during close(). This can 
> lead to inaccuracies in the timing, especially when the subplan is near the 
> end of a task pipeline, because other operator's times are calculated after 
> close, during deinitialize().



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to