hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kramer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-478) Surface "processor time" for queries
Date Fri, 10 Jul 2009 19:33:14 GMT

    [ https://issues.apache.org/jira/browse/HIVE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729787#action_12729787

Adam Kramer commented on HIVE-478:

Also, in case it was not obvious, the current system counts time going by while mappers/reducers
are "pending." This request would tell me how much time I actually used, e.g., not include
time spent waiting for mappers or reducers.

> Surface "processor time" for queries
> ------------------------------------
>                 Key: HIVE-478
>                 URL: https://issues.apache.org/jira/browse/HIVE-478
>             Project: Hadoop Hive
>          Issue Type: Wish
>          Components: Logging, Query Processor
>            Reporter: Adam Kramer
> We currently list real-time metrics of how long queries take--"finished in: 1min 13sec"
appears on the job tracker. However, this is affected by a lot more than just the quality
or implementation of the query. For example, number of mappers used varies a lot when you
use subqueries versus single-query aggregation, as does the amount of work necessary.
> For implementation comparisons (e.g., "should I use this version of the query or that
one"), ti would be great to know the processor time used instead of the real time used...both
in terms of "mapper cpu seconds" and "reducer cpu seconds."

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message