You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Mark Owens (JIRA)" <ji...@apache.org> on 2017/10/11 00:29:00 UTC
[jira] [Updated] (ACCUMULO-3329) Consider consolidation of "timing"
classes
[ https://issues.apache.org/jira/browse/ACCUMULO-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Owens updated ACCUMULO-3329:
---------------------------------
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.
was:
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 we 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.
> 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
> Labels: newbie
> Fix For: 2.0.0
>
>
> 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
(v6.4.14#64029)