[
https://issues.apache.org/jira/browse/ASTERIXDB-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761129#comment-17761129
]
ASF subversion and git services commented on ASTERIXDB-3239:
------------------------------------------------------------
Commit 2678d19660d6c982288cff4a4eb4db370026ecca in asterixdb's branch
refs/heads/master from Ian Maxon
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=2678d19660 ]
[ASTERIXDB-3239][API] Add profile summary to plan
- user model changes: yes
- storage format changes: no
- interface changes: no
Details:
If profiling is enabled, annotate the optimized plan
with the min & max time for each operator and connector
across partitions.
This can give a good idea of where the most time was
spent in a query generally.
Change-Id: I08b509fca0eb3ab9aad82e816dfe4849adf125ec
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17709
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Ian Maxon <ima...@uci.edu>
Reviewed-by: Ali Alsuliman <ali.al.solai...@gmail.com>
Contrib: Ian Maxon <ima...@uci.edu>
> Add summary profiling info to plan
> ----------------------------------
>
> Key: ASTERIXDB-3239
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3239
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: API - HTTP API, RT - Runtime
> Reporter: Ian Maxon
> Assignee: Ian Maxon
> Priority: Major
> Labels: triaged
>
> It would be nice if there were some summarized profiling information in the
> plan. The full profiler output is quite verbose and hard to interpret for
> large jobs or clusters with many partitions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
