Skip to content
Snippets Groups Projects
Select Git revision
  • 629-cookie-auth
  • develop default protected
  • master
  • 735-table-truncate
  • webdav
  • domain-policies
  • live-streaming
  • 303-json-ld
  • 0.18.2
  • 0.18.1
  • 0.18
  • 0.17
  • 0.16.3
  • 0.16.2
  • 0.16.1
  • 0.16
  • 0.15
  • 0.14.2
  • 0.14.1
  • 0.14
  • 0.13
  • 0.12
  • 0.11
  • 0.10
  • 0.9.1
  • 0.9
  • 0.8
  • 0.7
28 results
Blame Permalink
Forked from funkwhale / funkwhale
7163 commits behind the upstream repository.
optimization.rst 1.38 KiB

Optimizing your Funkwhale instance

Depending on your requirements, you may want to reduce as much as possible Funkwhale's footprint.

Reduce workers concurrency

Asynchronous tasks are handled by a celery worker, which will by default spawn a worker process per CPU available. This can lead to a higher memory usage.

You can control this behaviour using the --concurrency flag. For instance, setting --concurrency=1 will spawn only one worker.

This flag should be appended after the celery -A funkwhale_api.taskapp worker command in your :file:`docker-compose.yml` file if your using Docker, or in your :file:`/etc/systemd/system/funkwhale-worker.service` otherwise.

Note

Reducing concurrency comes at a cost: asynchronous tasks will be processed more slowly. However, on small instances, this should not be an issue.

Switch from prefork to solo pool

Using a different pool implementation for Celery tasks may also help.

Using the solo pool type should reduce your memory consumption. You can control this behaviour using the --pool=solo flag.

This flag should be appended after the celery -A funkwhale_api.taskapp worker command in your :file:`docker-compose.yml` file if your using Docker, or in your :file:`/etc/systemd/system/funkwhale-worker.service` otherwise.