Review `memory-static` CI jobs and take action
Context
We have a number of CI jobs that track memory usage in every pipeline:
- memory-on-boot (Test phase)
- memory-static (Test phase)
You could find them in any MR pipeline (except tests-only or docs-only ones).
memory-static
will load gems from the Gemfile and check the amount of RAM consumed as well as the number of objects allocated and retained.
Aggregated values will be included as 'metrics' into MRs while full reports will be downloadable as job artifacts.
memory-on-boot
is very similar but preloads the app in production env, hit it with a single request, and gather total gem memory consumption data using derailed exec perf:mem from derailed_benchmarks
More at https://github.com/zombocom/derailed_benchmarks
Problem
- Firstly, We need to check these jobs: make sure they are not broken, and provide useful data. Fix or tune if needed.
- If we are going to keep them, we need to increase the visibility. To start, we need to document them.
- Then, we need to make the results more discoverable. Currently, we post the results into the
metrics
section of every MR, but it doesn't seem to be used and is also very noisy. - We may consider a report, similar to
allure
ordanger-bot
in the MR comments, and/or some sort of stats in the longer run (on themaster
).
Edited by Aleksei Lipniagov