657 karma · joined August 30, 2014
See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/13344
We intend to keep both around as they serve different purposes :)
One thing these changes _should_ do is decrease the strain on the shared runners so you don't need to wait as long for the CI/CD pipelines to run. Right now we have some people/projects using a lot more resources than others, which was causing some of the back-up.
We can't really make the site faster only for specific users, and even if we could I don't think we would.
That said, with a proper revenue stream we'll be able to focus more resources toward performance on GitLab.com, so you should see continued improvement.
You can look through our issues labeled performance for GitLab CE[1], the infrastructure issue tracker[2], or our Gitaly project[3] for some examples of progress.
[1]: https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...
We have this demo from our most recent summit where we put together an entire GitLab instance in ~20 minutes on a Kubernetes cluster, though I'm not sure that's exactly what you want? https://about.gitlab.com/2017/01/23/video-tutorial-idea-to-p...
We also have some documentation on integrating with Kubernetes here: https://docs.gitlab.com/ee/user/project/integrations/kuberne...
https://drive.google.com/file/d/0ByoIqX0IDB5scWpJT0JKTHQtTG8...
We do want to open source it when we can.
EDIT: Previously said open source, open core is the correct term.
If you have any more information you can share, it'd be great if you could send it to peopleops at gitlab.com.
https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
If you don't want to do that in this thread, feel free to email me: connor at gitlab.com