You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Bikramjeet Vig (JIRA)" <ji...@apache.org> on 2018/04/17 23:05:00 UTC
[jira] [Resolved] (IMPALA-6120) Report actual CPU time for codegen
[ https://issues.apache.org/jira/browse/IMPALA-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bikramjeet Vig resolved IMPALA-6120.
------------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.13.0
> Report actual CPU time for codegen
> ----------------------------------
>
> Key: IMPALA-6120
> URL: https://issues.apache.org/jira/browse/IMPALA-6120
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.11.0
> Reporter: Tim Armstrong
> Assignee: Bikramjeet Vig
> Priority: Major
> Labels: codegen, supportability
> Fix For: Impala 2.13.0
>
>
> The codegen time measurements in profiles are often confusing because they're wall-clock time and can be inflated if a host is heavily loaded. We could use ThreadCounterMeasurement to get accurate user/sys CPU time.
> [~bikramjeet.vig] interested what you think of this since it was motivated by a discussion we had.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)