News for hackers. Stuff that matters.
Re:Degraded performance on GitLab.com by mr__y on Monday July 01, 2019 @12:33PM (#20327020)
exactly my experience. Assuming that a powerful enough server is available to do that. Our first attempt to run gitlab on some small cheap VPS (2 cores, 4 gigs of ram) was a total disaster.
Re:Degraded performance on GitLab.com by rococode on Monday July 01, 2019 @01:14PM (#20327521)
What server specs are working well for you?
Re:Degraded performance on GitLab.com by dijit on Monday July 01, 2019 @01:28PM (#20327644)
Not OP but I have a number of gitlab instances:

For 5 users we use 18G/4vCPU. For 20 users we use 32G/8vCPU

I keep asking to lower the footprint but the gitlab is the very definition of feature creep. And that comes at the cost of optimisation.

Re:Degraded performance on GitLab.com by aprdm on Monday July 01, 2019 @06:41PM (#20330441)
We support 30 developers on 10gb ram and 4 cores. That said, we are probably a year and a half behind version wise and only use it for its SCM capabilities.
Re:Degraded performance on GitLab.com by maverwa on Monday July 01, 2019 @06:43PM (#20330453)
We are running it on a 2vCore, 8GB RAM vm. Works good for our ~10 concurrent users on peak. The ~120CI builds per day are running on other hosts though.
Re:Degraded performance on GitLab.com by mr__y on Monday July 01, 2019 @01:41PM (#20327789)
quad core with 16 gigs of ram for a team of 4 people. Most likely 8gb of ram would be sufficient for us but the risk of decreasing our productivity is not worth the insignificant difference in price of 8GB vs 16GB VPS monthly fee.