Investigate `derailed perf:mem` results spikes
We noticed the running perf: mem
of the derailed benchmarks
sometimes gives us spikes.
We don't have a clear explanation, our best guess was that it could be related to GC runs, but the variance could be up to 30 MB
for the same library (gitlab/lib/google_api/cloud_platform/client.rb
), which is a lot.
It would be great to understand this:
- to make sure nothing shady happens with our app preload
- to understand the memory measurements better in general
Edited by Aleksei Lipniagov