This is not due to Ruby, both we and GitHub use that. We do offload some tasks to Go processes with GitLab workhorse to take advantage of multithreading. But th

This is not due to Ruby, both we and GitHub use that. We do offload some tasks to Go processes with GitLab workhorse to take advantage of multithreading. But therr are a few reasons GitLab.com is slow: 1. I didn't prioritize growing our infrastructure team after raising our A round, for a long time it was one person running GitLab.com. In the last couple of months I realized my error and now we're about 8 people and hiring. 2. We're shipping a lot of new features every month and we where not monitoring for performance regressions. We have better monitoring in place now. 3. GitLab.com runs on one file server. This release adds the capability to add multiple ones. We are also testing Ceph to make it completely distributed. 4. Some problems only occur at scale. GitLab.com is running GitLab Enterprise Edition with more than 500k accounts created. This causes problems that don't occur at 10k users. 5. Our monitoring infrastructure has been coarse. We're now using Prometheus to improve this.