Using Profiler class, from the utils package, instead of System.currentTimeMillis() #524
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Yesterday I found out that some methods' execution time are being measured based on System.currentTimeMillis() calls. We have a Profiler class, under the com.cloud.utils package, so I'm trying to make the use of that class consistent.
The PR is split in 2 commits: one for the formatting changes; and the other for applying the Profiler usage.