News for hackers. Stuff that matters.

A comment on Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool. Parent comment

Re:Take Gitlab to the command line with GLab, an open-source... by mattl on Thursday August 06, 2020 @02:56AM (#24068729)
How much RAM? Are you installing from Omnibus packages? I ask because I have two servers and have near perfect uptime.
[ Parent | on HN ]
Re:Take Gitlab to the command line with GLab, an open-source... by ianbooker on Thursday August 06, 2020 @04:34AM (#24069131)
64 GB on a 16 core machine that has nothing else to do.

If any, I think this is maybe too much, every worker just spawns more and more workers. I restricted Postgres from taking all RAM, Sidekiq and Puma to low numbers. But there are more..

I follow the instructions straight from Gitlab.

[ Parent | on HN ]
Re:Take Gitlab to the command line with GLab, an open-source... by brodock on Thursday August 06, 2020 @08:10AM (#24070220)
Consider having databases in a separate instance. 2x32GB is better than one 64GB.

It's specially important at this size to have git in a different machine than the database as both are I/O constrained.

[ Parent | on HN ]