Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • reliability reliability
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,809
    • Issues 1,809
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Scheduled maintenance on the database layer will take place on 2022-07-02. We expect GitLab.com to be unavailable for up to 2 hours starting from 06:00 UTC. Kindly follow our status page for updates and read more in our blog post.

  • GitLab.com
  • GitLab Infrastructure Team
  • reliabilityreliability
  • Issues
  • #59
Closed
Open
Created Apr 11, 2016 by Sid Sijbrandij@sytsesOwner

Make GitLab.com fast

Moved to https://gitlab.com/gitlab-com/infrastructure/issues/947


GitLab.com is not fast enough. Speed measurements:

  • GitHub.com issue https get => current historic: 1,520 ms on 2016-07-15
  • GitLab.com issue https get => current historic: 741 ms on 208-01-02 | 1,095 on 2017-09-23 | 6,052 ms on 2016-06-23 | 2,095ms on 2016-07-15 after 8.10.rc | 1,493 ms on 2016-10-11 after 8.12.5 order by fix
  • dev.gitlab.org issue https get => current historic: 570 ms on 2016-07-25

Issue as an authenticated user is pretty representative https://performance.gitlab.net/dashboard/db/gitlab-web-status?refresh=1m&panelId=14&fullscreen&orgId=1&from=now-30d&to=now

You can see how we're working to improve the speed of GitLab in:

  1. Performance issues for GitLab https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&state=opened&utf8=%E2%9C%93&label_name%5B%5D=Performance
  2. Performance issues for our infrastructure https://gitlab.com/gitlab-com/infrastructure/issues?scope=all&state=opened&utf8=%E2%9C%93&label_name%5B%5D=performance

Currently our 99% request response time is more than 5 seconds. By the dates below 99% of GitLab http(s) requests will take less than the mentioned time:

  • under 2 seconds at the end of 2016
  • under 1 second at the end of 2017
  • under 500ms at the end of 2018
Edited Jan 02, 2018 by Sid Sijbrandij
Assignee
Assign to
Time tracking