Brother there’s nothing to capitalize on. They really don’t want an avalanche of free users bringing their shit down too I think.
replyGitlab used to be about as reliable as github. (ignoring the security oopses they used to have)
replyThey simply don't have (or didnt) the skills to scale. THey were talking about using ceph to run things (which gives you an idea about how green their infra team was)
Are you implying they should create more in-house solutions, or that specifically Ceph is not a good solution and there is some other 3rd party solution that could be used instead?
replyWhat's wrong with Ceph?
replyWhats right with it?
replyIts slow, large, excessively complex and not that resilient to failure.
You either want a bunch of NFS machines backed on to ZFS on nvme, with a central jumping off point that allows sharding (this is critical to allow one or more NFS server to fuck up and not kill access to everything else.)
Or, pay the money and use GPFS
companies using paid github are in same spot. Tho I'd imagine many already moved over
replyMost companies signing up to the idea that GitHub will fix their issues, rather than going through operational pain of migration. Everyone that I know jokes about GH downtime, but have zero internal talks about migration. Obviously small data point, but GitLab going this route shows not a lot of people are switching.
replyUnless you pay for enterprise then you are on the Enterprise Cloud Instance:
https://us.githubstatus.com/posts/dashboard
replyI've never actually seen that status page before, and I'm not clear what it's measuring. My company pays for Enterprise Cloud, and we see all the same downtime as what gets posted to https://www.githubstatus.com/
replyThat is the ghe.com status page, which it seems like no one actually uses, hence the good uptime. Most Enterprise Cloud customers don’t use it.
replyhttps://docs.github.com/en/enterprise-cloud@latest/admin/dat...
Yeah, but they could make it up in volume.
replyI'm not sure there's a lot to capitalize on, considering the state of hosting OSS development. But this really is a case study on watching your biggest competitor face plant into a wall, and responding by breaking into a head first sprint.
reply