Project

General

Profile

Bug #33445

Increase pulpcore-api worker count and make it configurable

Added by Eric Helms 11 months ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:

Description

\n\n*Description of problem:*\nwe currently configure the api service to only have a single worker:\n\n/etc/systemd/system/pulpcore-api.service\n\nExecStart=/usr/libexec/pulpcore/gunicorn pulpcore.app.wsgi:application \\\n --timeout 90 \\\n -w 1 \\\n\n\nGenerally this is fine, but we've seen some conditions where this isn't enough and can lead to errors. I think we should likely increase the default to something higher (4?) and make it configurable."

Associated revisions

Revision 2da99656 (diff)
Added by Eric Helms 10 months ago

Fixes #33445: Increase default API gunicorn worker count

This increases the default API gunicorn worker count to be similar
to that of content worker count but with a smaller minimum. There
are different workloads that can require higher throughput through
the API and the current default of 1 is too low of a starting point.

History

#1 Updated by The Foreman Bot 11 months ago

  • Assignee set to Eric Helms
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-pulpcore/pull/226 added

#2 Updated by Ewoud Kohl van Wijngaarden 11 months ago

  • Triaged changed from No to Yes
  • Category set to Foreman modules
  • Subject changed from b'increase pulpcore-api worker count and make it configurable' to Increase pulpcore-api worker count and make it configurable

#3 Updated by The Foreman Bot 10 months ago

  • Pull request https://github.com/theforeman/puppet-pulpcore/pull/231 added

#4 Updated by Eric Helms 10 months ago

  • Status changed from Ready For Testing to Closed

#5 Updated by Evgeni Golov 10 months ago

  • Found in Releases 3.1.0 added

Also available in: Atom PDF