Details
-
Wish
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
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."