Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitlab was down

status.gitlab.com

Post reply on HN
Print view View original

121–130 of 140 posts

Re: Gitlab was down

#121

Post by apple4ever »

dijit wrote: post #26

Notably they don’t hire any real people with ops experience. Erring instead to go for developers hoping that they can do everything needed. I like gitlab as a product but they don’t have a service mindset, and I think not hiring operations-centric people is a symptom of that which causes these kinds of issues.

My anecdotal experience: I applied to a SRE position, and I have 10 years of experience in system engineering and 5 years in dev ops. I didn’t even get an interview. I’m not saying I would have or should have gotten the job, but they at least should have interviewed me.

Re: Gitlab was down

#122

Post by apple4ever »

ramchip wrote: post #83
kungtotte wrote: post #73

Earlier quoted context omitted.

Whenever GitHub is down you see comments saying much the same thing only with the names reversed. The thing that strikes me each time is how fragile everyone's setup is if GitHub/lab is a single point of failure for them... At least gitlab let's you self host, which would let you run backups on offsite hosting meaning zero downtime.

Github also supports self-hosting.

Yes but not for free.

Re: Gitlab was down

#123

Post by apple4ever »

jeltz wrote: post #113
niceworkbuddy wrote: post #67

Earlier quoted context omitted.

GitLab has virtual machine image, so it's really unobtrusive for your system.

They also have a Debian package with sets up the whole environment. It has worked well for me so far. The only thing I had to add was a backup script.

The omnibus package makes it real easy to install, especially with Ansible.

FYI if you are uploading to AWS or other cloud providers, you don’t even need a backup script. You can configure it in the gitlab.rb file:

https://docs.gitlab.com/ee/raketasks/backup_restore.html#upl...

Re: Gitlab was down

#125

Post by AdamJacobMuller »

chriscool wrote: post #106
1337shadow wrote: post #87

Earlier quoted context omitted.

Let me clarify: git clone/fetch/push on gitlab.com or github.com is sluggish, but on my private instances it's blazing fast, because I get great and un-metered bandwidth from my dedicated servers which might not be the case for everybody / every country. Another thing: CI starts the very second I push, and since I configure dedicated runners extremely well GitLab makes it easy keep every pipeline stage under 5 minute…

> pushing to gitlab prints out the URL to create a pull request from that branch You can use push options to automatically create a pull request and set it up when you push: https://docs.gitlab.com/ee/user/project/push_options.html

Had no idea that existed, super cool, thanks!

Re: Gitlab was down

#126

Post by lbotos »

oefrha wrote: post #74
frant-hartm wrote: post #71

Earlier quoted context omitted.

From my experience a custom GitLab instance is much faster that GitHub.com. But it is apples and oranges and I suppose your friends weren't comparing the two.

My custom GitLab instance is still slower than github.com. (Yes, I’m giving it enough memory.)

If you are a customer you can file a support ticket and our Support Engineers can help troubleshoot. One of our mandates is "performance is a feature" and we want to better understand what's happening in the wild.

If not, and you are interested, we built a tool we use called "fast-stats": https://gitlab.com/gitlab-com/support/toolbox/fast-stats

it might be able to pinpoint what controllers are slow for your own curiosity.

Re: Gitlab was down

#127

Post by oefrha »

lbotos wrote: post #126
oefrha wrote: post #74

Earlier quoted context omitted.

My custom GitLab instance is still slower than github.com. (Yes, I’m giving it enough memory.)

If you are a customer you can file a support ticket and our Support Engineers can help troubleshoot. One of our mandates is "performance is a feature" and we want to better understand what's happening in the wild. If not, and you are interested, we built a tool we use called "fast-stats": https://gitlab.com/gitlab-com/support/toolbox/fast-stats it might be able to pinpoint what controllers are slow for your own curio…

I'm a community user, and the sluggishness seems to be a common sentiment so I'm not sure profiling my instance will add anything valuable that's not already known.

(Sorry if my comments sounded entitled.)

Re: Gitlab was down

#128

Post by Dayshine »

scaryclam wrote: post #100
Dayshine wrote: post #49

Earlier quoted context omitted.

Gitlab is still the only viable choice for non-commercial groups who want private repos though, the 3 private members and no ability to have mixtures of public/private repos in organisations on Github is very limiting.

Sorry, but this isn't true at all. Bitbucket works fine, and GitHub offers plans for non-profit groups for free: https://github.com/nonprofit Self-hosting has multiple different options as well.

Registered non-profit non-commercial.

- a private website for my local sailing club. - a mod for a game - an open source project that requires a private repository for a few things - any project relating to a private community

None of these are registered non-profits.

Bitbucket is capped at 5 users as far as I can see, and self-hosting is just a recipe for lost data. I don't know of many amateur groups that can safely host a server.

Re: Gitlab was down

#129

Post by KptMarchewa »

kungtotte wrote: post #120
Cthulhu_ wrote: post #114

Earlier quoted context omitted.

Zero downtime is an ideal that you'd need a lot of investment for to achieve. I mean for 99.99999% uptime you'd already need to have a multi-server, multi-AZ, multi-region and multi-cloud setup and orchestrate data parity between those environments. That's not easy to set up and maintain.

Yes. Tell that to all the companies that have to stop working when either of these sites go down because they've built their entire workflow on GitHub/lab being up. Since zero downtime is so costly, maybe it's a better idea not to rely on the uptime of a third party?

You're wrongly assuming that your own service will have a better uptime.

Re: Gitlab was down

#130

Post by intellix »

Not sure if I have anything else to add on top of what people are already saying but the performance of GL is extremely frustrating for the past couple of months. Viewing the diff of a PR can sometimes take around 20 seconds just to load the tab.

I think it's about time they dedicated some resources or addressed the public about the efforts they're making to address these issues. It's becoming excruciating.

I've used Github every day for years and years and I feel like every page load has been pretty much instant forever.

Post reply on HN