You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/01/21 21:02:00 UTC

[jira] [Resolved] (IMPALA-5651) Investigate cheaper stack trace printing mechanism

     [ https://issues.apache.org/jira/browse/IMPALA-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-5651.
-----------------------------------
    Resolution: Later

Not a bad idea, but we've fixed the perf problem by disabling symbolisation: IMPALA-7014

> Investigate cheaper stack trace printing mechanism
> --------------------------------------------------
>
>                 Key: IMPALA-5651
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5651
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.9.0
>            Reporter: Matthew Jacobs
>            Priority: Major
>              Labels: observability, perfomance
>
> In IMPALA-5275, [~mmokhtar] identified several code paths where Status() was printing expensive stack traces in performance sensitive code. That JIRA is being used to track fixing those individual cases, but we should also investigate if we can print stack traces in a more efficient manner in general.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)