Fix incorrect ns to ms conversion in Metrics
#538
Merged
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.
Description
Rather than just fix the conversion, I've changed the Metrics class to take ms directly as input because it also returns ms. This keeps the units consistent to prevent confusion in calling code.
Fixes
MetricsforStoreinstances incorrectly converts NS to MS #535Type of Change
Testing
Updated the unit tests and used the following script to validate (1)
mainrecords the time wrong and (2) this branch does it right.The times for
Write time (ms)andstore.put.connectorshould be similar (and not off by 1000x).Pull Request Checklist
Please confirm the PR meets the following requirements.
pre-commit(e.g., mypy, ruff, etc.).