You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2016/03/18 02:25:33 UTC
[jira] [Updated] (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 ]
Julian Hyde updated CALCITE-1085:
---------------------------------
Fix Version/s: (was: next)
avatica-1.7.1
> 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: avatica-1.7.1
>
>
> 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)