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 Mon, 07 Feb 2011 23:00:57 GMT

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

Adam Kramer commented on HIVE-478:
----------------------------------

Sorry for the month-long delay. This is all I need. But it would be great, in general, to
report this in the standard way:

Time taken: 185.89 seconds (23,194,570 CPU_MILLISECONDS)

...in the CLI. Otherwise ok to mark issue resolved.

> Surface "processor time" for queries
> ------------------------------------
>
>                 Key: HIVE-478
>                 URL: https://issues.apache.org/jira/browse/HIVE-478
>             Project: 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message