[
https://issues.apache.org/jira/browse/ACCUMULO-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-3329.
-----------------------------------------
Resolution: Not A Problem
Fix Version/s: (was: 2.0.0)
This is an old issue, and much has changed since this issue was created. If
this is still an issue, please consider opening a new issue at
https://github.com/apache/accumulo/issues
> Consider consolidation of "timing" classes
> ------------------------------------------
>
> Key: ACCUMULO-3329
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3329
> Project: Accumulo
> Issue Type: Improvement
> Components: client, master, tserver
> Reporter: Josh Elser
> Priority: Major
> Labels: newbie
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
