I know many devs who use Macs and I can't figure it out why could be Docker so painfully slow on Mac it's almost unusable, do all those people run to Ubuntu? I know there are also small aps and Docker might be much faster with those but still. Without it it's not 20 but more like 100x times slower and almost unusable :( It works like a charm on all kinds of Linuxes but it's roughly 20 to 50x times slower on Mac (I'm using Docker for Mac as I'm not really great with Docker and not devops for sure). Gitlab_rails = falseĪre there any performance tweaks, I could make? GitLab.I'm using rather big PHP based project with MySQL, ElasticSearch & Redis. Gitlab_rails = 'production-gitlab-redis'Įxternal_url ' gitlab_rails = 26 gitlab/postgresql:/var/lib/postgresql/dataĬontainer_name: production-gitlab-website I am using the following configuration for a self hosted gitlab installation via docker-compose.
Packed PostgreSQL and Redis into an extra container, outside of Gitlab. Increased the maximum ram a puma worker can get until it gets restarted to 1250 megabytes. Set the puma threads to 4 (min and max), see Requirements | GitLab. Increased the puma workers to 5 (cpu cores - 1), from Requirements | GitLab. Most affected are the repository pages in web ui (for example What I did already:. Then the intial request takes only 263ms. The slow response time disappears when the exact same repository has been viewed a few times in web UI. It could be the API response time which is slow, since curl -I returns X-Runtime: 2.230676 for example. An initial page load (for example of a repository) takes multiple seconds, this can be seen in the network tab of the browser (the initial request takes most of the time, at least 2 seconds the DOM is then ready in more than 3 seconds). I am experiencing overall slow performance on my gitlab installation, even though it is locally running.Īre there any performance tweaks to make? This should not be an hardware issue (6 cores, 12 threads, 16GB DDR4 RAM, running on an SATA SSD).
0 kommentar(er)
