Skip to content

Run Pipeline page (/pipelines/new) is slow to load

Summary

This was reported by a customer. Refer ZD(internal) for more details.

The project in question has more than 2400 branches and 30,000 tags.

Doing a profiling on the page reveals that DOMContentLoaded takes around 17 seconds while the page finishes loading in 18 seconds.

Relevant profiling details below:

<snip>
"https://gitlab.example.com/namespace/project/-/pipelines/new"
"active-record: 40ms"
"es: 0ms"
"gitaly: 0ms"
"host: null"
"redis: 748ms"
"total: 3197 | 3170 |  20976"
--
"/namespace/project/-/pipelines/config_variables"
"active-record: 4ms"
"es: 0ms"
"gitaly: 0ms"
"host: null"
"redis: 1ms"
</snip>

Steps to reproduce

Can be partially reproduced by visiting: https://gitlab.com/gitlab-org/gitlab/-/pipelines/new

Example Project

https://gitlab.com/gitlab-org/gitlab/

What is the current bug behavior?

DOMContentLoaded takes long so that the Run Pipeline page is loading slow.

What is the expected correct behavior?

Run Pipeline page should load faster.

Relevant logs and/or screenshots

Browser freezes on this screen until the page is loaded.

Screenshot_2021-02-17_at_2.38.28_PM

Output of checks

This bug happens on GitLab.com as well.

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:check SANITIZE=true)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)

(we will only investigate if the tests are passing)

Possible fixes

Edited by Miguel Rincon