4 ms·
Their performance graph shows response timings up to 25 seconds [1]. GitHub's mean web response time goes up to 200 milliseconds. The difference is two orders o
by praseodym 11y ago
Their performance graph shows response timings up to 25 seconds [1]. GitHub's mean web response time goes up to 200 milliseconds. The difference is two orders of magnitude. Is GitLab really that much slower?!
[1] https://about.gitlab.com/images/8_5/issue_timings.png https://about.gitlab.com/images/8_5/issue_timings.png
[2] https://status.github.com/ https://status.github.com/
- Keats 11y agoIt is extremely slow. We tried it on a 1go droplet and it felt slow with 2 users but can't beat that £0 price.
- sytse 11y agoJust so you know, we recommend a minimum of 2GB https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md#memory https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...
- mrmondo 11y agoHave you tried running GitHub EE on something of the same spec? It's terrible to near impossible and it doesn't include nearly as many of the features as Gitlab. We have been running Gitlab for 100~ employees for well over a year on a single, medium/low specced VM and its lightning quick, so much so that when Devs/Ops have to use GitHub you can hear the sighs around the office!
- sytse 11y agoGlad to hear GitLab is fast for you! Will be even faster with 8.5 :)
- mrmondo 11y agoSeriously Sytse, Gitlab has not only continued to improve, it's done so at rockets pace while (and here's the hard part) at the same pace also improved quality and test coverage. Do you remember a year or so ago when I was whinging about some regressions after several upgrades? Well I'll tell you what - there hasn't been any that have impacted us in such a long time upgrades - even to a major version - do not worry me one bit and our Devs are always excited to see what's new. I'm not sure if you remember but we're a non-profit, charitable organisation and GitLab has really helped us immensely over the past year. A damn fine product from a damn fine team, supported by a damn fine community.
- sytse 11y agoThank you for your kind words. I'm very glad to hear our quality is improving and you're having pain-free upgrades. We're proud that GitLab allows everyone to contribute, even organizations without a large budget https://about.gitlab.com/strategy/ https://about.gitlab.com/strategy/ Thanks for using GitLab and writing about it https://smcleod.net/mirror-gitlab-to-github/ https://smcleod.net/mirror-gitlab-to-github/
- Can_Not 11y ago> medium/low specced VM Can you be more specific? Does that mean 1core+512MB? Is 8core+12GB considered medium to you? Is that 100 Programmers or 50 Programmers plus 50 issue commented? Totally agree on GHEE. I have 4 Programmers+4commenters running on a $200/month recommended hosting partner and it's performance is not up to my expectations (especially when I'm the only one on...)
- YorickPeterse 11y agoThat's the 95th percentile, not the mean. This means that 95% of all transactions completed _within_ the time, with only 5% exceeding it. Right now our 95th percentile hovers between 1.5 and 2 seconds, the mean hovers between 500 and 700 ms.
- morgante 11y agoGitHub's 98th percentile is still just 414ms though. So you still have a lot of catching up to do.
- jobvandervoort 11y agoWe're aware. GitHub did an amazing job on scaling GitHub.com. We'll get there!
- dogweather 11y agoYour 95th percentile ought to be 200ms. That's the standard that Google set for itself a decade ago.
- jobvandervoort 11y agoNote that this is 95th percentile and the peak is _before_ the changes of 8.5 _and_ that this is data of GitLab.com that has problem not typical for a GitLab instance. That said, we're fully aware of the shortcoming of GitLab.com. It has been slow and unresponsive. We're working hard on improving it [0] and this release has been a step in that. [0]: https://gitlab.com/gitlab-com/operations/issues/42 https://gitlab.com/gitlab-com/operations/issues/42