Post 9vA0PE3iDXSIIk5vk0 by czero1@mastodon.technology
(DIR) More posts by czero1@mastodon.technology
(DIR) Post #9v9nDqw2YGvpzjkjYG by sir@cmpwn.com
2020-05-18T02:23:32Z
1 likes, 2 repeats
https://docs.gitlab.com/ee/administration/operations/unicorn.html#unicorn-worker-killertl;dr:"GitLab has memory leaks."Their solution is monkey patching their application to check its memory usage after every 16th HTTP request and commit suicide if it's too much. This page is telling sysadmins who install their own GitLab instance how to configure this.
(DIR) Post #9v9oJkcn1j2e7B7o2a by sir@cmpwn.com
2020-05-18T02:37:46Z
3 likes, 1 repeats
You know, I empathise with GitLab here. git.sr.ht had a memory leak once. My solution was pretty interesting: I wrote a shell script on a cronjob set to every 5 minutes, which checked the heap size of the git.sr.ht backend and, if it was within a certain percentage of system memory, it sent a SIGTERM along andWait, no, none of that is what happened. What happened is I fixed the memory leak.
(DIR) Post #9v9oeVq5C7O6L6F5wO by cindyping@m.cmx.im
2020-05-18T02:41:01Z
0 likes, 0 repeats
@sir this solution is rather quite elegant and future proof
(DIR) Post #9v9pYYcm1eWfC7k29A by sir@cmpwn.com
2020-05-18T02:51:43Z
1 likes, 0 repeats
I'm hitting the new git.sr.ht API backend 100x/sec with a non-trivial query and it's using 4M of RAM and 2% of one CPU core
(DIR) Post #9v9plHEbzX0b1fVNWi by sir@cmpwn.com
2020-05-18T02:53:54Z
2 likes, 0 repeats
OH MY GODThere are MORE pages detailing how to kill memory hungry GitLab processes in MORE situations and with MORE approaches catered to your PARTICULAR OOM killing needshttps://docs.gitlab.com/ee/administration/operations/sidekiq_memory_killer.html
(DIR) Post #9v9rYdfFUGYGjZ48Yq by riking@social.wxcafe.net
2020-05-18T03:13:52Z
0 likes, 0 repeats
@sir this is horrid even for rails
(DIR) Post #9v9wCqa7HQtSCD5qts by rozenglass@mstdn.io
2020-05-18T04:05:17Z
2 likes, 2 repeats
@sir We wanted to install Gitlab on our Kubernetes cluster at work. Gitlab provides official installation charts.> In order to deploy GitLab on Kubernetes, the following are required:> A Kubernetes cluster, version 1.12 or higher. 8vCPU and 30GB of RAM is recommended.This was unthinkable when the backend for our main project uses 80MBs of RAM. Needless to say, we scraped the idea, and just installed Gitea and Jenkins (Not perfect, but better than throwing away 30GBs).
(DIR) Post #9v9wQrsbFb1UHBQNrE by sir@cmpwn.com
2020-05-18T04:08:39Z
2 likes, 0 repeats
@rozenglass jeesh, that's insane
(DIR) Post #9v9wt9mYHcNhuM5Jwm by lanodan@queer.hacktivis.me
2020-05-18T04:14:30.592676Z
1 likes, 0 repeats
@sir > sidekiq_memory_killerOh, reminds me that mastodon admin had/have to pull similar shitty tricks.
(DIR) Post #9v9yKFhaTsfs2cFM8G by flussence@nulled.red
2020-05-18T04:29:42Z
0 likes, 0 repeats
@sir I remember the days when PHP's per-request limit was 8MB and anything demanding higher limits was rightly considered a war crimeEven MediaWiki only needs 20MB
(DIR) Post #9vA0PE3iDXSIIk5vk0 by czero1@mastodon.technology
2020-05-18T04:52:48Z
0 likes, 0 repeats
@sir meanwhilehttps://simon.shimmerproject.org/2020/04/30/xfce-switches-to-gitlab/XFCE switches to gitlabhttps://about.gitlab.com/press/releases/2019-09-17-gitlab-adopted-by-KDE.htmlgitlab adopted by KDEcorporate lobbying, now in "open source" (tm)
(DIR) Post #9vAC2rBTmczIR4pNxI by kline@cmpwn.com
2020-05-18T07:01:25Z
0 likes, 0 repeats
@czero1 @sir do you have any evidence of the conspiracy (non-snark, genuine interest and use of the word).I only ask because another project I knew wanted an integrated source forge, and at the time the only real option was GitLab and Phabricator.
(DIR) Post #9vASzOxjx7TrGBL7PE by lasombra@fosstodon.org
2020-05-18T10:13:10Z
0 likes, 0 repeats
@sir I'm quite surprised to have read something like this.
(DIR) Post #9vAUwBMSGWUM7EUaWW by af@social.librem.one
2020-05-18T10:36:02Z
0 likes, 0 repeats
@sir the next top paying job will be to fix the memory leaks in all this crap software. Start learning valgrind.
(DIR) Post #9vAcxrcdQPWh6nNCd6 by Conan_Kudo@fosstodon.org
2020-05-18T12:02:48Z
0 likes, 0 repeats
@sir @rozenglass I'm happy that Pagure still stays within those nice reasonable buckets. In the *high end*, deployments need at most 4GB of RAM, and most deployments get away with 1GB of RAM or less for *everything* (pagure, redis, pgsql). If it didn't, I don't think I could run it for my personal use on my tiny VM...
(DIR) Post #9vAgyeZRppF4jjVxgm by Paul@ruby.social
2020-05-18T12:49:44Z
0 likes, 0 repeats
@sir I've been a rails developer since the beginning, and have delt with many memory leaks. It's pretty hard to leak memory in Ruby itself, the vast majority of the time it's from deep within C extensions, like imagemagik or libxml.
(DIR) Post #9vAlsJJSSS7qq7pX6m by csravens@toot.cafe
2020-05-18T13:44:28Z
0 likes, 0 repeats
@sir this has always been the problem with rails
(DIR) Post #9vArAStk3gnBYEHHl2 by Coffee@toot.cafe
2020-05-18T14:43:45Z
0 likes, 0 repeats
@sirClever! By counting to exactly 16, they only need 4 bits to store the counter, saving some valuable memory!
(DIR) Post #9vAuaRdXfcAt1ymQiG by gudenau@mastodon.technology
2020-05-18T15:20:32Z
0 likes, 0 repeats
@sir No, just no.
(DIR) Post #9vHqUYNoeCbEUJVmaG by shine@mastodon.technology
2020-05-21T23:39:21Z
0 likes, 0 repeats
@sir I hope you did notice there was a section called 'Switch to Puma' right above the page's link in the navigation sidebar."As of GitLab 12.9, Puma has replaced Unicorn. as the default web server. [...]Why switch to Puma?Puma has a multi-thread architecture which uses less memory than a multi-process application server like Unicorn. [...]"source : https://docs.gitlab.com/ee/administration/operations/puma.html