[ACCUMULO-3329] Consider consolidation of "timing" classes

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Component/s: client, master, tserver
• Labels: newbie
• Assignee: Unassigned
• Reporter: Josh Elser
• Created: 13/Nov/14 00:45
• Updated: 11/Jun/19 04:20
• Resolved: 11/Jun/19 04:20

Description

We have a number of "timing" classes in or used by the codebase

• org.apache.accumulo.core.util.StopWatch
• org.apache.accumulo.core.util.OpTimer
• Traces
• Guava's Stopwatch

I'm assuming that consolidation of all of the timings into Traces would be the best (assuming that if we care about the timing of a given operation implies that twe would also care about the timing of the "bigger picture").

If we can remove some of our timer classes, that would be great. Not suggesting that we forcibly prevent the use of Stopwatches/TImers in the codebase entirely – just where it makes sense.

Issue Links

• is related to: ACCUMULO-1242 Consistent logging