You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TotalExecutionTime is tracked on execute() but not on queue().
This is not a problem with the normal executionTime metric around the run() method, but the total end-to-end metric.
For queue() we want to track from the time queue() is invoked until the time the underlying thread completes and a Future.get() could retrieve the value even if it doesn't.
We don't want to track until Future.get() is invoked as that is not the actual processing time of the execution and can be variant depending on what the client code is doing.
This was a known missing feature but I'm marking this as a bug as it should have been there before marking the 1.0 release.
The text was updated successfully, but these errors were encountered:
Here is a screenshot showing before (green) and after (red) on a command that is only executed asynchronously so previously did not capture TotalExecutionTime but now does.
The TotalExecutionTime is tracked on execute() but not on queue().
This is not a problem with the normal executionTime metric around the run() method, but the total end-to-end metric.
For queue() we want to track from the time queue() is invoked until the time the underlying thread completes and a Future.get() could retrieve the value even if it doesn't.
We don't want to track until Future.get() is invoked as that is not the actual processing time of the execution and can be variant depending on what the client code is doing.
This was a known missing feature but I'm marking this as a bug as it should have been there before marking the 1.0 release.
The text was updated successfully, but these errors were encountered: