4 ms·
I like GitLab but noticed my Docker container running it is steadily requiring more memory to run smoothly. It’s sitting at 12GB right now, which is a little t
by marmaduke 8y ago
I like GitLab but noticed my Docker container running it is steadily requiring more memory to run smoothly. It’s sitting at 12GB right now, which is a little too high for my taste. I wish there were ways to reduce this.
- pknopf 8y agoI occasionally have to rm my docker instance and recreate it. I'm not sure what it's doing, but at least it's an easy fix.
- russh 8y agoI have the same issue. Every once in a while the docker instance will get into a endless loop trying to start up and failing. So far the only fix I have found is to remove and recreate the instance. Still, I love having my own local GitLab.
- lbotos 8y agoOne of our Engineering Fellows is working Memory Optimization across the entire product this quarter. We are aware, and starting on it!
- sytse 8y agoThat fellow would be Stan, the person who just commented with https://news.ycombinator.com/item?id=18972052 https://news.ycombinator.com/item?id=18972052
- stanhu 8y agoCould you show the output of `ps aux` inside the container? Also note that GitLab Omnibus will add more Unicorn processes the more available RAM it has in the system. You can turn off that automatic scaling by lowering the number of processes via https://docs.gitlab.com/omnibus/settings/unicorn.html https://docs.gitlab.com/omnibus/settings/unicorn.html.
- marmaduke 8y agoThanks for the reply, here's my late response. I've pasted the output of ps aux here https://gist.github.com/maedoc/1f6e568d44541d7734204d294c98a661 https://gist.github.com/maedoc/1f6e568d44541d7734204d294c98a..., though now it seems to have dropped significantly. The only change I seemed to have made that could account for that is moving from a local disk storage to NFS storage, maybe there's some caching accounting effect..