From 18bef721f612515855b5ebfcbccf3e6c4b09695f Mon Sep 17 00:00:00 2001 From: reivilibre Date: Thu, 14 Apr 2022 14:25:57 +0000 Subject: deploy: 7efddbebefbadce3e5f0938ea123e7e37ad2503c --- develop/workers.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'develop/workers.html') diff --git a/develop/workers.html b/develop/workers.html index eb90c68507..788fa244d7 100644 --- a/develop/workers.html +++ b/develop/workers.html @@ -428,9 +428,9 @@ the full URI, or even just round robin), the room ID is the path component after of events, then a dedicated set of workers can be provisioned to limit the effects of bursts of events from that bridge on events sent by normal users.

Stream writers

-

Additionally, there is experimental support for moving writing of specific -streams (such as events) off of the main process to a particular worker. (This -is only supported with Redis-based replication.)

+

Additionally, the writing of specific streams (such as events) can be moved off +of the main process to a particular worker. +(This is only supported with Redis-based replication.)

To enable this, the worker must have a HTTP replication listener configured, have a worker_name and be listed in the instance_map config. The same worker can handle multiple streams, but unless otherwise documented, each stream can only @@ -486,7 +486,7 @@ the stream writer for the presence stream:

^/_matrix/client/(api/v1|r0|v3|unstable)/presence/

Background tasks

-

There is also experimental support for moving background tasks to a separate +

There is also support for moving background tasks to a separate worker. Background tasks are run periodically or started via replication. Exactly which tasks are configured to run depends on your Synapse configuration (e.g. if stats is enabled).

-- cgit 1.4.1