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

Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/02/12 00:18:18 UTC

[jira] [Resolved] (CALCITE-1085) NoopTimer#start should not create a new NoopContext for every invocation

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

Josh Elser resolved CALCITE-1085.
---------------------------------
    Resolution: Fixed

Fixed in https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=de7759112cea3deb8a1c75bcc43753adbe8648de

> NoopTimer#start should not create a new NoopContext for every invocation
> ------------------------------------------------------------------------
>
>                 Key: CALCITE-1085
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1085
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: next
>
>
> Just noticed that I forgot to make NoopTimer return a singleton NoopContext from {{#start}}. This is going to increase the burden for metrics for the noop case, potentially creating a lot of garbage on the heap.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)