Pair with teams for deeper understanding of what we see in Go Continuous Profiler's graphs
In &200, we made it possible to use GCP's stackdriver profiler with GitLab-Pages, Workhorse, and Gitaly. We made the relevant teams aware of the tool, and created some content to assist the teams in using it.
Since this is the sort of thing we should keep an eye on, we should spend some time with an engineer from each team to understand how they interpret the flame graphs so that we have a better idea of what is expected vs what is abnormal in the graphs.
Proposal
For each service:
- identify engineers to join on a call
- set up the call
- and record the call.
| Service | Engineers to work with | Sync call booked? | Link to notes from call | Recording |
|---|---|---|---|---|
| Gitaly | @zj-gitlab @pks-t @samihiltunen | 2020-09-16 12:00UTC | https://docs.google.com/document/d/1OTSiwk3Yk_B0yJbyKh08PH_bkdgJnLQlkZD6VKV-xNk/edit# | https://youtu.be/3TSO_evSi5Q |
| Workhorse | @mkaeppler @igorwwwwwwwwwwwwwwwwwwww @jacobvosmaer-gitlab @alipniagov | 2020-09-23 12:00UTC | https://docs.google.com/document/d/1VeMi4Gbu1BZ_oAchTo_RcemaORFFV-Mgqe_fuPcbmVg/edit# |
|
| GitLab-Pages | @vshushlin, @jaime (couldn't join the call) | 2020-10-05 12:30UTC | https://docs.google.com/document/d/1q0yV-tStK8PRIWKMoPlowJzOvCwsIYBzvZVWEM2buh0/edit# | https://youtu.be/K7dYSnO0gns |
| Registry | @jdrpereira | 2020-10-07 14:30UTC | https://docs.google.com/document/d/13y5OzBEB41o25OIJiI4Qj5ioLvXBwkPRQFf739Zi1Wk/edit#heading=h.1jtqalr9tko7 | https://youtu.be/pZZEvysCyrg |
Edited by Bob Van Landuyt