Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update deploy-jobs.md #1181

Merged
merged 1 commit into from
Mar 13, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions admin-guide/en/deploy-jobs.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,8 @@ Every server should be configured with _one_ of the following methods for runnin

### Workers

For large sites, we recommend using the worker mode together with a supervisor-like application to process the jobs.
The worker will run as a daemon, wait for jobs to be dispatched, execute a single job and quit. Once the worker quits, the supervisor will create another instance of it to process the remaining jobs.
System resources can be allocated to the worker so that it will not cause spikes in resource usage that slow down the main site.
For large sites, we recommend using a worker to process jobs. The worker, when run as a daemon, will wait for jobs to be dispatched and then run them one-by-one in a separate process on the server.
System resources can be specifically allocated to the worker so that it will not cause spikes in resource usage that slow down the main site.

The following command can be used to initialize a worker.

Expand Down Expand Up @@ -217,4 +216,4 @@ Jobs should never be run while the site is under maintenance, for example during

---

Learn more about handling [user accounts](./deploy-users).
Learn more about handling [user accounts](./deploy-users).
Loading