-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Changing the number of workers
Proxymiity ☆ edited this page Apr 29, 2021
·
5 revisions
When you run vaultwarden, it spawns 2 * <number of cpu cores>
workers to handle requests. On some systems this might lead to low number of workers and hence slow performance, so the default in the docker image is changed to spawn 10 threads. You can override this setting to increase or decrease the number of workers by setting the ROCKET_WORKERS
variable.
In the example below, we're starting with 20 workers:
docker run -d --name vaultwarden \
-e ROCKET_WORKERS=20 \
-v /vw-data/:/data/ \
-p 80:80 \
vaultwarden/server:latest
- Which container image to use
- Starting a container
- Updating the vaultwarden image
- Using Docker Compose
- Using Podman
- Building your own docker image
- Building binary
- Pre-built binaries
- Third-party packages
- Deployment examples
- Proxy examples
- Logrotate example
- Overview
- Disable registration of new users
- Disable invitations
- Enabling admin page
- Disable the admin token
- Enabling WebSocket notifications
- Enabling Mobile Client push notification
- Enabling U2F and FIDO2 WebAuthn authentication
- Enabling YubiKey OTP authentication
- Changing persistent data location
- Changing the API request size limit
- Changing the number of workers
- SMTP configuration
- Translating the email templates
- Password hint display
- Disabling or overriding the Vault interface hosting
- Logging
- Creating a systemd service
- Syncing users from LDAP
- Using an alternate base dir (subdir/subpath)
- Other configuration