Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(metrics): separate a avm call time & interpretation time metrics #1893

Merged
merged 7 commits into from
Nov 10, 2023

Conversation

gurinderu
Copy link
Contributor

@gurinderu gurinderu commented Nov 10, 2023

Description

Separate an AVM call time & interpretation time metrics.

Motivation

For now, the interpretation time metric shows as the interpretation time + disk IO time. We want to expose information without IO to clearly understand the AVM behavior.

Proposed Changes

interpretation_time becomes time from AVM metrics and shows only interpretation.
call_time is a previous interpretation_time.

Checklist

  • The code follows the project's coding conventions and style guidelines.
  • All tests related to the changes have passed successfully.
  • Documentation has been updated to reflect the changes (if applicable).
  • All new and existing unit tests have passed.
  • I have self-reviewed my code and ensured its quality.
  • I have added/updated necessary comments to aid understanding.

Reviewer Checklist

  • Code has been reviewed for quality and adherence to guidelines.
  • Tests have been reviewed and are sufficient to validate the changes.
  • Documentation has been reviewed and is up to date.
  • Any questions or concerns have been addressed.

Copy link

linear bot commented Nov 10, 2023

NET-626 Use `execution_time` from AVMOutcome

Report it as a separate metric

Compare against old Interpretation Time metric

@gurinderu gurinderu changed the title fix(metrics): separate a avm call time & interpretation time metrics fix(metrics): separate a avm call time & interpretation time metrics Nov 10, 2023
@gurinderu gurinderu marked this pull request as ready for review November 10, 2023 10:32
let call_time_sec = Histogram::new(execution_time_buckets());
sub_registry.register(
"avm_call_time_sec",
"Distribution of time it took to run the avm call once",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see much difference between "time it took to run the interpreter once" and "time it took to run the avm call once". Can you write clearer ones?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

avm call time is an interpratation time + saving data on disk

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cool, would be nice to reflect it in the metrics descriptions, wdyt?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@folex folex merged commit e94d1e4 into master Nov 10, 2023
12 checks passed
@folex folex deleted the feature/net-626 branch November 10, 2023 15:50
gurinderu added a commit that referenced this pull request Nov 14, 2023
…1893)

* fix(metrics): separate a avm call time & interperation time metrics

* fix comment

* fix comment

* improve fmt

* improve desc

* add retries
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants