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

perf tests: use metrics for memory usage charts #5565

Merged
merged 3 commits into from
Jul 13, 2023

Conversation

algorandskiy
Copy link
Contributor

@algorandskiy algorandskiy commented Jul 12, 2023

Summary

Current heapwatch tooling uses only pprof heap profile for memory usage charts and reports although there are runtime metrics collected and available.

  1. client_ram_report.py uses both heap and metrics
  2. plot_crr_csv.py renders charts using all the data from (1)
  3. additionally excluded account lookups in pinpong for pure payment tests

Test Plan

Tested locally, chart sample attached. The solid line is the old pprof data, all non-solid lines are new from runtime metrics.
Primary heap2 csv

@codecov
Copy link

codecov bot commented Jul 13, 2023

Codecov Report

Merging #5565 (73fd792) into master (aeef625) will increase coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #5565      +/-   ##
==========================================
+ Coverage   55.80%   55.83%   +0.02%     
==========================================
  Files         446      446              
  Lines       63417    63418       +1     
==========================================
+ Hits        35389    35407      +18     
+ Misses      25663    25650      -13     
+ Partials     2365     2361       -4     
Impacted Files Coverage Δ
shared/pingpong/pingpong.go 0.00% <0.00%> (ø)

... and 6 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

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

Successfully merging this pull request may close these issues.

3 participants