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

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: avatica-1.7.0
• Component/s: avatica
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 11/Feb/16 19:29
• Updated: 29/Apr/19 17:14
• Resolved: 11/Feb/16 23:18

Description

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.