Topic: Investigate used gems
Problem to solve
Try to see which loaded gems are the biggest, and try to remove them from the codebase. Try to understand if these gems can be executed externally.
Proposal
Use derailed_benchmarks to measure the size of used gems
Split gems into groups like web and worker
Rails loads all the gems by default but we can discriminate the gems loaded by Puma (Rails) and Sidekiq (Rails). Related to https://www.gregnavis.com/articles/how-to-reduce-memory-usage-by-tuning-gemfile.html
Links / references
🤖
Auto-Summary Discoto Usage
Points
Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive)
point:
. For example, the following are all valid points:
#### POINT: This is a point
* point: This is a point
+ Point: This is a point
- pOINT: This is a point
point: This is a **point**
Note that any markdown used in the point text will also be propagated into the topic summaries.
Topics
Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.
Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive)
topic:
. For example, the following are all valid topics:
# Topic: Inline discussion topic 1
## TOPIC: **{+A Green, bolded topic+}**
### tOpIc: Another topic
Quick Actions
Action Description /discuss sub-topic TITLE
Create an issue for a sub-topic. Does not work in epics /discuss link ISSUABLE-LINK
Link an issuable as a child of this discussion
Last updated by this job
-
⏫ ROOT GitLab 1.8GB/2GB Focus https://gitlab.com/groups/gitlab-org/memory-team/-/epics/2 -
◀ PARENT Investigate used gems https://gitlab.com/groups/gitlab-org/memory-team/-/epics/2#note_446589283