Gitlab is pretty awesome. The interface makes it easy to use.
Ask HN: GitHub vs. Gitlab?
61–70 of 113 posts
Re: Ask HN: GitHub vs. Gitlab?
#62I'm using Gitlab right now, and honestly I wish I'd chosen GitHub instead. Self-hosted Gitlab requires maintenance (Sidekiq randomly dies, needs manual restart), upgrading is a pain, and (for me) when I tried exporting my projects from self-hosted Gitlab to Gitlab.com tbe import failed with a "unable to decompress" error on Gitlab.com! I'm too tied to Gitlab now with all the wiki pages, issues, etc. but I'm left disa…
Are you using this Omnibus packages? See https://about.gitlab.com/downloads/
That should solve the Sidekiq restarts and the upgrades https://twitter.com/johann_sonntag/status/745791831225544704
Re: Ask HN: GitHub vs. Gitlab?
#63I haven't used GitHub a ton, but GitLab is really crappy in my experience. I'm constantly frustrated by the UX. CVSweb and Trac do a better job, and did so 10 & 15 years ago. I've also used BitBucket quite a bit; it's not great, but it's a ton better than GitLab.
How can we improve the UX to remove your frustration?
Re: Ask HN: GitHub vs. Gitlab?
#64Earlier quoted context omitted.
At a high level, what are the major areas where you face performance issues? Does the choice of RoR play a part in performance problems? Can performance be improved by deploying more servers? PS: I really enjoy using Gitlab, and would be ready to replace Github with Gitlab in my workflow if the performance improves.
My understanding (as a frontend engineer, so I'm not as intimately familiar with the problems as some others are) is that the biggest bottleneck at this point is with the file system. We're working on switching to CephFS which looks very promising. See the relevant issue for more info: https://gitlab.com/gitlab-com/operations/issues/1 I can get someone from the backend performance team to comment too if you'd like :)
> I can get someone from the backend performance team to comment too if you'd like :)
Sure!
> the biggest bottleneck at this point is with the file system.
Would something like AWS EFS [1] solve the problem?
It might not be a practical solution from a cost perspective though. Eg: for 50TB of data at $0.3/GB/month
0.3*1024*50 = $15360/month
Re: Ask HN: GitHub vs. Gitlab?
#65I quite like GitLab, although I'm using it self hosted on premises for our team. Honestly, it's overkill and I wish Gogs had been more evolved when I initially picked up GitLab. I have not really tried GitLab's hosted offering, I have a couple repos up there, but nothing extensive. Have you considered a VPS with Gogs? It's super lightweight and easier than snot to setup.
Have you checked our RhodeCode ? It's much more mature that Gogs.
Re: Ask HN: GitHub vs. Gitlab?
#66Earlier quoted context omitted.
You're right, we have to do better on performance. We solved most of the time waiting when pushing a new commit, see the API timings slide on https://www.scribd.com/doc/316471059/GitLab-Infrastructure-2... The web interface is still slower than we like. We've doubled the team of performance engineers and we're making progress, see https://gitlab.com/gitlab-com/infrastructure/issues/59 and all issues labeled with perf…
At a high level, what are the major areas where you face performance issues? Does the choice of RoR play a part in performance problems? Can performance be improved by deploying more servers? PS: I really enjoy using Gitlab, and would be ready to replace Github with Gitlab in my workflow if the performance improves.
Hi dineshp, I'm Pablo Carranza, and I am currently leading the effort on infrastructure at GitLab, this includes performance.
> what are the major areas where you face performance issues? > Does the choice of RoR play a part in performance problems?
RoR does not play a part in the performance problems as much as any other language choice. Our performance problems come from at least 3 different fronts: lack of caching in some specific points making us call the same complex/slow operations many times, NFS (filesystem) performance as a whole, and algorithms that worked really well at small scale, but not anymore, both at app level and at DB level.
I think that RoR is a really good option for building a product fact, and eventually it is necessary to start specializing specific parts that do not perform anymore, and just replacing what cannot be specialized. The key element here is that we need to measure first to see where the problem is.
> Can performance be improved by deploying more servers?
Not really, more front end servers means more load on the NFS backend, so there is no easy solution here. The first step into fixing this issue right now is this one: https://gitlab.com/gitlab-com/infrastructure/issues/139 and then we will start playing with a distributed FS as a longer term solution: https://gitlab.com/gitlab-com/operations/issues/1
As a final note, we are using some specific issues to measure performance as a blackbox, and those issues are seeing some really good progress lately. So stay tuned :)
Re: Ask HN: GitHub vs. Gitlab?
#67Earlier quoted context omitted.
At a high level, what are the major areas where you face performance issues? Does the choice of RoR play a part in performance problems? Can performance be improved by deploying more servers? PS: I really enjoy using Gitlab, and would be ready to replace Github with Gitlab in my workflow if the performance improves.
Hi dineshp, I'm Pablo Carranza, and I am currently leading the effort on infrastructure at GitLab, this includes performance. > what are the major areas where you face performance issues? > Does the choice of RoR play a part in performance problems? RoR does not play a part in the performance problems as much as any other language choice. Our performance problems come from at least 3 different fronts: lack of caching…
Thank you for the helpful answer!
Could you also comment on this https://news.ycombinator.com/item?id=12056991
Re: Ask HN: GitHub vs. Gitlab?
#68I quite like GitLab, although I'm using it self hosted on premises for our team. Honestly, it's overkill and I wish Gogs had been more evolved when I initially picked up GitLab. I have not really tried GitLab's hosted offering, I have a couple repos up there, but nothing extensive. Have you considered a VPS with Gogs? It's super lightweight and easier than snot to setup.
Have you checked our RhodeCode ? It's much more mature that Gogs.
I really like the mirror feature on Gogs, the Gogs ui, the easy deployment using Docker and that it uses Go so the memory and cpu usage is quite low.
Re: Ask HN: GitHub vs. Gitlab?
#69I tried signing up for Gitlab some months ago, and automated emails to my fastmail-hosted email address didn't get delivered. My blocking concern is that email delivery problems, if they persist, will hurt the site's usefulness. (For all I know this is already fixed.)
Re: Ask HN: GitHub vs. Gitlab?
#70For me it's very simple as I only use them for Git repos. We use Jira and other tools for other needs.
Github - I use it for public projects because, it's the most popular site so larger pool of people.
Gitlab - It's free to put your private repos here so, this is where I store all my infrastructure code.