Commit Graph

10 Commits

Author SHA1 Message Date
GitLab Bot 4279dbc29c Add latest changes from gitlab-org/gitlab@master 2022-11-15 15:08:26 +00:00
GitLab Bot 6bed1b9c9c Add latest changes from gitlab-org/gitlab@master 2022-11-09 21:07:34 +00:00
GitLab Bot 2e2c1a521c Add latest changes from gitlab-org/gitlab@master 2022-08-10 18:12:05 +00:00
GitLab Bot 5bc7c18ad3 Add latest changes from gitlab-org/gitlab@master 2022-03-02 12:15:38 +00:00
GitLab Bot c59765a50a Add latest changes from gitlab-org/gitlab@master 2020-06-24 18:09:03 +00:00
Nick Thomas 6ce21a9c17
Add a predicate to check for strong memoization 2019-09-10 13:45:21 +01:00
Thong Kuah 8c42a0eac0 Add frozen_string_literal to lib part 2
Using the sed script from
https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
2019-08-23 00:15:24 +12:00
Zeger-Jan van de Weg 428c38a2b1
Fix rubocop offence 2017-12-12 17:40:54 +01:00
Zeger-Jan van de Weg 3ab026b7d6
Use memoization for commits on diffs
The Gitaly CommitService is being hammered by n + 1 calls, mostly when
finding commits. This leads to this gRPC being turned of on production:
https://gitlab.com/gitlab-org/gitaly/issues/514#note_48991378

Hunting down where it came from, most of them were due to
MergeRequest#show. To prove this, I set a script to request the
MergeRequest#show page 50 times. The GDK was being scraped by
Prometheus, where we have metrics on controller#action and their Gitaly
calls performed. On both occations I've restarted the full GDK so all
caches had to be rebuild.

Current master, 806a68a81f, needed 435 requests
After this commit, 154 requests
2017-12-12 16:28:26 +01:00
Lin Jen-Shin (godfat) 258bf3e187 Add Gitlab::Utils::StrongMemoize 2017-11-13 15:27:30 +00:00