Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #8784

Closed
Open
Created Feb 12, 2015 by Administrator@rootOwner

Error 502 when rendering big commits

Created by: apazdnikov

Hello.

First of all - Thank you very much for such a great product Gitlab is.

Have faced with a 502 timeout problem when looking diffs after upgrading from 7.0 -> 7.7.

  1. big diffs
  2. diffs with submodule promotion to another commit

Have made an example commit of a big file at a public test project on gitlb.com https://gitlab.com/apazdnikov/test-very-slow-rendering/commit/576ec96bbce1db759a517d429569d2883c243b63

It renders about a minute. At mine installation it fails with 502 error with increased timeouts in unicorn up to 290 seconds.

How can help investigate and solve this problem?

Thank you.

Assignee
Assign to
Time tracking