Date: Mon, 04 Jan 2021 18:28:38 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 252416] www/gitlab-ce may need more workers configured in puma.rb Message-ID: <bug-252416-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252416 Bug ID: 252416 Summary: www/gitlab-ce may need more workers configured in puma.rb Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: mfechner@FreeBSD.org Reporter: gwright@antiope.com Assignee: mfechner@FreeBSD.org Flags: maintainer-feedback?(mfechner@FreeBSD.org) Hi, When upgrading the gitlab-ce port to version 13.7.1, I noticed intermittent failures of some pages. For example, navigating to the Repository -> Graph page would spin forever, never rendering the repository network graph. After fumbling about, I noticed that after the switch from unicorn to puma I had not updated my puma configuration to match my unicorn.rb. My GitLab instance has several dozen projects, with sizes from tens of MB to about one GB. In the file ```config/puma.rb```, the number of workers was still at the default value = of 3. I bumped it up to 8 and the problem disappeared. Evidently I was runni= ng out of workers which would stall the rending of complex pages. Here is the change I made: ``` root@gitlab:/usr/local/www/gitlab-ce # git diff config/puma.rb.sample config/puma.rb diff --git a/config/puma.rb.sample b/config/puma.rb index 02bf6de..3a24376 100644 --- a/config/puma.rb.sample +++ b/config/puma.rb @@ -33,7 +33,7 @@ queue_requests false # accepted protocols. bind 'unix:///usr/local/www/gitlab-ce/tmp/sockets/gitlab.socket' -workers 3 +workers 8 require_relative "/usr/local/www/gitlab-ce/lib/gitlab/cluster/lifecycle_events" require_relative "/usr/local/www/gitlab-ce/lib/gitlab/cluster/puma_worker_killer_initializer" root@gitlab:/usr/local/www/gitlab-ce # ``` This is not strictly a bug, but the documentation should note that the defa= ult number of puma workers is perhaps only suitable for testing and needs to be increased on a production server. Don't know why I didn't hit this earlier (the change in default server from unicorn to puma occurred around 13.5), but I since I am back at work I am stressing my gitlab instance more. Thanks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252416-7788>